*** Binbin has joined #openstack-meeting | 00:31 | |
*** jakedahn has quit IRC | 00:47 | |
*** jakedahn has joined #openstack-meeting | 00:47 | |
*** adjohn has joined #openstack-meeting | 01:06 | |
*** dcramer_ has joined #openstack-meeting | 01:14 | |
*** kd9261 has joined #openstack-meeting | 01:17 | |
*** spectorclan_ has joined #openstack-meeting | 01:51 | |
annegentle | we'll get started in about a minute, hi everyone | 01:59 |
---|---|---|
spectorclan_ | hi | 01:59 |
*** alandman has joined #openstack-meeting | 01:59 | |
deshantm | hi | 01:59 |
dcramer_ | Hello. | 02:00 |
deshantm | o/ | 02:00 |
annegentle | glad the time didn't throw everyone off too much :) I've got 9:00 so I'll get started | 02:01 |
annegentle | #startmeeting | 02:01 |
openstack | Meeting started Tue Jun 7 02:01:30 2011 UTC. The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot. | 02:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 02:01 |
annegentle | #Goal-setting for this meeting | 02:01 |
*** toddmorey has joined #openstack-meeting | 02:02 | |
annegentle | I basically wanted to get doc/web aficionados together regularly to talk about what's going on with docs and the website | 02:02 |
*** med_out is now known as med | 02:02 | |
*** med is now known as medberry | 02:02 | |
annegentle | especially now that we're looking for ways to open up the openstack.org site for more people to work on it | 02:03 |
annegentle | I think it's good to review doc bugs, too. | 02:03 |
annegentle | Plus, try to coordinate doc tasks. | 02:03 |
spectorclan_ | annegentle: can you clarify your open up the openstack.org site for others to work on | 02:04 |
annegentle | Any other goals you want to bring up? Have for this meeting? I'm open to suggestions and agenda items | 02:04 |
kd9261 | I think it would be beneficial to standardize a layout for tutorial wiki pages. i.e. installation guides | 02:04 |
annegentle | sure, toddmorey has been working on ways to get a core group of reviewers for the openstack.org site just like we do code reviews | 02:04 |
spectorclan_ | annegentle: that makes sense, ok. had not heard that before | 02:05 |
annegentle | kd9261: honestly, I think my hope is to consolidate installation information to just a few pages | 02:05 |
*** j1mc has joined #openstack-meeting | 02:05 | |
annegentle | kd9261: 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 docs | 02:06 |
kd9261 | annegentle: That's a good idea, there are just some specifics b/w different distributions/OS | 02:06 |
annegentle | kd9261: 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 |
annegentle | kd9261: I appreciate the wiki edits if you're the one who worked on 'em today by the way :) | 02:07 |
annegentle | Vish asked me to consolidate install information this release, so it's certainly a good doc task | 02:08 |
kd9261 | annegentle: I am a strong believer of readbility. Especially when new Open Stack users come along (I am one) | 02:08 |
j1mc | annegentle: did you mean that the installation instructions "aren't" quite ready for that? | 02:08 |
annegentle | j1mc: more like, are the installations on distros equivalent yet? | 02:08 |
annegentle | j1mc: oh yes, "are/aren't" thanks :) | 02:08 |
j1mc | ah, ok - thanks for clarifying | 02:08 |
kd9261 | annegentle: From my [little] experience, they are different enough to justify having separate pages, the landing page is very clear though | 02:09 |
annegentle | one additional goal for this meeting is to get input on doc priorities | 02:09 |
annegentle | kd9261: ok, good to know | 02:09 |
annegentle | kd9261: and I think your instinct is correct | 02:09 |
annegentle | I 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-away | 02:10 | |
annegentle | we 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 IRC | 02:11 | |
annegentle | spectorclan_: yes, or at least installation instructions can consistently point to the correct place | 02:12 |
spectorclan_ | ok, just saw the link. It makes sense and works easily. I like very much | 02:12 |
annegentle | need to redo the topic, hang on | 02:12 |
* j1mc looks at a couple of 'installation doc' examples that come to mind... | 02:12 | |
annegentle | #topic Goal-setting for this meeting | 02:12 |
*** openstack changes topic to "Goal-setting for this meeting" | 02:12 | |
kd9261 | something like this is very appealing: http://www.ubuntu.com/download | 02:12 |
kd9261 | the postgres is more "professional" looking | 02:13 |
spectorclan_ | kd9261: I think it just depends on the look/feel of the existing site | 02:13 |
kd9261 | #agree | 02:13 |
annegentle | kd9261: yeah, to me, ubuntu appeals to any end-user, we need to appeal to cloud/server admins | 02:13 |
deshantm | annegentle: agree that audience matters, I was just going to make a similar comment | 02:14 |
annegentle | spectorclan_: 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 thinking | 02:14 |
annegentle | kd9261: but simple is good too :) | 02:14 |
toddmorey | the 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 specific | 02:15 |
medberry | I see no dependencies on the Postgresql page. Is that your intent. | 02:15 |
j1mc | http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/ | 02:15 |
kd9261 | medberry: those should be in the specific distro page | 02:15 |
j1mc | annegentle: 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 |
alandman | I think there needs to be something more clearly organized then the wiki since finding the content on it can be far from easy | 02:15 |
annegentle | medberry: ah good point, but yeah they change based on OS, right? | 02:15 |
medberry | annegentle, 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 wiki | 02:16 |
annegentle | j1mc: 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 example | 02:16 |
annegentle | spectorclan_: yes, released, tested, from 3rd party sources, that sort of category | 02:17 |
spectorclan_ | 3rd party? Hmm, would we then post a release from StackOps? | 02:17 |
j1mc | yes! 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 |
annegentle | j1mc: yes that's a great install guide, guess it might be time to separate out to a new install guide | 02:17 |
annegentle | j1mc: awesome, thanks to toddmorey and dcramer_ | 02:18 |
annegentle | ok, I think we're okay with goal-setting, on to next (thanks for the input on install as well) | 02:18 |
j1mc | annegentle: that fedora docs setup is done in docbook, and it all output through fedora/redhat's publican | 02:18 |
annegentle | oh and should I do some actions for install doc and download page? Anyone? | 02:18 |
annegentle | j1mc: yes I learned a bit about publican this weekend at Open Help as well :) | 02:19 |
annegentle | #topic General documentation status - RST on each project | 02:19 |
*** openstack changes topic to "General documentation status - RST on each project" | 02:19 | |
kd9261 | annegentle: I have 3 months to dedicate to wiki install doc editing | 02:20 |
kd9261 | my group is very active on an Open Stack trunk | 02:20 |
annegentle | kd9261: you hooked on wiki? :) Can we talk more about an install book in docbook or you like wiki better? | 02:20 |
kd9261 | annegentle: I am not up to speed on terminlogy, sorry | 02:21 |
annegentle | kd9261: ok, no worries :) | 02:21 |
kd9261 | I like the install book a lot, however it would have to gaurantuee complete accuracy otherwise lessons learned by one user don't propogate as well | 02:21 |
annegentle | #link http://wiki.openstack.org/Documentation/HowTo | 02:21 |
annegentle | that page describes the areas where doc lives, wiki is just a small part | 02:21 |
annegentle | accuracy is a huge part of Vish's request, answering the same questions over and over is no fun | 02:22 |
annegentle | so I completely agree | 02:22 |
annegentle | So the swift.openstack.org site is built from RST housed in the Swift source code, and it was updated with their 1.4 release | 02:23 |
annegentle | Other than the swift RST docs, that is the only activity so to speak that I know of. | 02:23 |
kd9261 | annegentle: from a new user perspective, it is nice to have lots of documentation but confusing when it is duplicated in multiple places | 02:24 |
kd9261 | its unclear which is most accurate, despite that install book looks much mre polished | 02:24 |
annegentle | kd9261: agreed. | 02:24 |
annegentle | kd9261: the install docs are the top priority there | 02:24 |
annegentle | kd9261: as far as removing duplicates | 02:25 |
annegentle | ideally, 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 project | 02:25 |
annegentle | kd9261: so that gives the high-level overview of what goes where and also hints at why duplication occurs - both audiences need to know some information | 02:25 |
deshantm | it's an audience thing again. devs vs. sysadmins right? | 02:26 |
annegentle | #topic General documentation status - DocBook docs in openstack-manuals project | 02:26 |
*** openstack changes topic to "General documentation status - DocBook docs in openstack-manuals project" | 02:26 | |
kd9261 | annegentle: agreed. Being a new developer and user I can appreciate both views. Development hinges on being able to successful install first. | 02:27 |
annegentle | deshantm: 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 docbook | 02:27 |
annegentle | kd9261: yes, absolutely. I find the sysadmins can install no problem but configuration confounds them. | 02:27 |
annegentle | The status of the DocBook docs - I have merged all requests in and I busily update it about daily. | 02:28 |
kd9261 | annegentle: this is exactly the case. | 02:28 |
deshantm | kd9261: 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 yet | 02:28 |
annegentle | I'm working on incorporating CC licensed content in the DocBook content from bloggers whom I've contacted, such as kpepple | 02:29 |
* deshantm is working to fix that one | 02:29 | |
annegentle | I 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 |
kd9261 | There is very little in the way of Dashboard as well. I am working alongside a colleague who has come to this realization | 02:30 |
annegentle | there 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 |
j1mc | annegentle: I just emailed you the contact info for the Ubuntu translations coordinator in case it might be helpful. | 02:31 |
annegentle | j1mc: thanks a bunch :) | 02:31 |
annegentle | today I added a short chapter about hypervisors | 02:32 |
annegentle | and we now have automated builds that automatically copy the trunk docs to docs.openstack.org/trunk, but there is no landing page with CSS yet | 02:33 |
annegentle | #link http://docs.openstack.org/trunk/ | 02:33 |
annegentle | (yep, ugly, but automated is good) | 02:33 |
kd9261 | #agreed | 02:33 |
annegentle | I'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 |
toddmorey | that's what I was wondering... | 02:34 |
deshantm | maybe better to have the trunk look different | 02:35 |
toddmorey | Maybe on docs.openstack, but visually separated just a bit | 02:35 |
toddmorey | and below the other options, I would think | 02:35 |
deshantm | so that users don't think it is official by mistake when it is still in progress | 02:35 |
annegentle | also, 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 commenting | 02:35 |
annegentle | deshantm: good point | 02:35 |
spectorclan_ | would a user really want to see the trunk docs version? | 02:35 |
toddmorey | I like the idea of some sort of "trunk" banner at the top of those pages… just in case you stumble into one via google search | 02:36 |
deshantm | spectorclan_: OpenStack users probably will | 02:36 |
annegentle | spectorclan_: 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 easily | 02:36 |
toddmorey | shoot, we could even tell google not to spider trunk… not sure how people feel about that | 02:36 |
deshantm | annegentle: agree with that | 02:36 |
spectorclan_ | ok, just checking. As long as we clarify what each section is, we should be fine | 02:36 |
annegentle | spectorclan_: 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 trunk | 02:37 |
dcramer_ | We've added support for a banner to the webhelp format recently. | 02:37 |
annegentle | deshantm: yes I like the idea of a banner | 02:37 |
annegentle | #link http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.1/content/index.html | 02:37 |
annegentle | shows the - DRAFT - banner on the API 1.1 document | 02:38 |
spectorclan_ | cool | 02:38 |
annegentle | toddmorey: I like telling Google not to search trunk, it only adds to the "duplication" I scream in my head :) | 02:38 |
annegentle | oh 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 |
annegentle | billing! | 02:39 |
deshantm | annegentle re: Google ...yeah, clouds, you can't trust them ;) | 02:39 |
annegentle | deshantm: hee | 02:39 |
toddmorey | billing? | 02:40 |
j1mc | annegentle: neat idea in telling google to not search trunk | 02:40 |
annegentle | my guess is, they want to know if you get plug-n-play billing when you get OpenStack running | 02:40 |
deshantm | toddmorey: 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 |
toddmorey | ah… yes indeed. and here I thought altruism powered the world | 02:41 |
annegentle | soon, 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 that | 02:41 |
*** dcramer_ has quit IRC | 02:41 | |
annegentle | toddmorey: do you mind talking some about the openstack.org project's status? | 02:42 |
annegentle | #topic General status for openstack.org project | 02:42 |
*** openstack changes topic to "General status for openstack.org project" | 02:42 | |
toddmorey | I get it now. I was thinking from a user perspective, and wondering who had CC statements with OpenStack, LCC on them. :) | 02:42 |
toddmorey | Sure thing! | 02:42 |
annegentle | toddmorey: heh, right. This is the words being input on docs.openstack.org in the Google Custom Search Engine | 02:42 |
annegentle | thanks | 02:42 |
toddmorey | We 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 |
deshantm | toddmorey: which CMS did you guys go with? | 02:44 |
toddmorey | First 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 |
toddmorey | The CMS is called Silverstripe. It's an open source PHP framework… the closest thing in PHP to django. | 02:45 |
toddmorey | The site now has versioned content and consumes other data via RSS or JSON, depending on the source | 02:45 |
toddmorey | that'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 videos | 02:47 |
toddmorey | spectorclan_: I mean a project to show up here: https://bugs.launchpad.net/openstack/+filebug | 02:48 |
j1mc | toddmorey: 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/Website | 02:49 |
toddmorey | j1mc: 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-meeting | 02:50 | |
toddmorey | no, sorry… I mean the website itself should be a (minor) openstack project, the way manuals currently is. Make sense? | 02:50 |
annegentle | I'm thinking more like we need a project for openstack-web (or something) so bugs can be listed like https://bugs.launchpad.net/openstack-manuals | 02:50 |
spectorclan_ | toddmorey: yep, get it | 02:51 |
*** Binbin has quit IRC | 02:51 | |
toddmorey | what Anne said. :) | 02:51 |
toddmorey | bugs and to have ammo for these meetings to prioritize the next projects for the site | 02:51 |
deshantm | oh i found a bug the participating companies is different on the home page and community page | 02:52 |
* j1mc nods | 02:52 | |
deshantm | 76 vs. 65 | 02:52 |
toddmorey | for 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 |
annegentle | deshantm: good catch | 02:52 |
spectorclan_ | deshantm: we add about 2 or 3 partners a day - very busy getting legal processing completed; | 02:53 |
toddmorey | that 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 listing | 02:53 |
j1mc | i'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 |
annegentle | ok, do we name the project openstack-web, openstack-website? | 02:53 |
spectorclan_ | openstack-website sounds better to me | 02:54 |
deshantm | better do website | 02:54 |
annegentle | j1mc: yeah we'll put the notes up | 02:54 |
deshantm | web might be a admin panel someone write | 02:54 |
annegentle | true, who knows it might be taken | 02:54 |
toddmorey | openstack-website: very clear | 02:54 |
annegentle | #action toddmorey and annegentle to work with ttx on making openstack-website project | 02:55 |
j1mc | thanks... it sounds like you're off to a good start. i'll catch up with you all later. | 02:55 |
annegentle | j1mc: thanks Jim | 02:55 |
toddmorey | thanks, j1mc! | 02:55 |
j1mc | yw :) good night! | 02:55 |
annegentle | ok, last topic, bugs | 02:55 |
spectorclan_ | toddmorey: we need to put translations onto our long term list so we can have multiple languages | 02:55 |
*** zul has quit IRC | 02:55 | |
annegentle | #topic Doc bugs | 02:55 |
*** openstack changes topic to "Doc bugs" | 02:55 | |
annegentle | For example, see https://bugs.launchpad.net/nova/+bugs?field.tag=documentation | 02:56 |
toddmorey | spectorclan_: translation support is ready when we are! | 02:56 |
annegentle | We are currently tracking doc bugs per project and also within the lp:openstack-manuals project | 02:56 |
spectorclan_ | toddmorey: ok, let's talk offline as I have people ready to help us now | 02:56 |
annegentle | The bug lists are managed by ttx and myself mostly, we move them between projects as needed also | 02:56 |
annegentle | Bugs 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 | |
annegentle | and I will wrap up in 3 minutes, with the last topic | 02:57 |
annegentle | #topic Open discussion | 02:58 |
*** openstack changes topic to "Open discussion" | 02:58 | |
toddmorey | annegentle: good sell! | 02:58 |
medberry | tx annegentle | 02:58 |
spectorclan_ | awesome! | 02:58 |
medberry | thanks all. | 02:58 |
annegentle | medberry: thanks for the comments on the doc site, keep 'em coming :) | 02:58 |
deshantm | annegentle: is there RSS subcribe for bugs? | 02:58 |
annegentle | deshantm: hm, good question, there's a link on the page to subscribe by email but dunno about RSS | 02:59 |
annegentle | #action annegentle to ask ttx about RSS and subscribing to doc bug feeds | 02:59 |
spectorclan_ | i only see bug email | 02:59 |
deshantm | I have a lot of emails that I filter so I might miss the bugs in email | 03:00 |
deshantm | I would rather have a way to make sure I get all xen-related documentation things | 03:00 |
annegentle | deshantm: yeah and I'm realizing I'd like to flag doc bugs in my email so it's a good question | 03:00 |
deshantm | I follow the XenServer wiki page via email, so that is OK | 03:00 |
medberry | you can probably use a 3rd party RSS-izer... | 03:01 |
deshantm | but I don't like launchpad bug mail since it tends to be noisy and hard to filter | 03:01 |
annegentle | OK, good. Well thanks everyone for coming. | 03:01 |
toddmorey | thanks, annegentle! this is a good step forward. | 03:01 |
annegentle | I'll post notes to the wiki page linked from http://wiki.openstack.org/Meetings/DocTeamMeeting | 03:01 |
spectorclan_ | exit | 03:01 |
spectorclan_ | oops | 03:01 |
annegentle | #endmeeting | 03:01 |
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 03:01 | |
openstack | Meeting ended Tue Jun 7 03:01:58 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 03:02 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-02.01.html | 03:02 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-02.01.txt | 03:02 |
openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-02.01.log.html | 03:02 |
*** spectorclan_ has quit IRC | 03:02 | |
annegentle | toddmorey: yes, I'm jazzed! | 03:02 |
deshantm | bye | 03:02 |
annegentle | deshantm: g'night | 03:02 |
*** alandman has quit IRC | 03:02 | |
medberry | gnite | 03:02 |
*** medberry is now known as med_out | 03:02 | |
*** toddmorey has quit IRC | 03:03 | |
*** dwcramer has quit IRC | 03:08 | |
*** j1mc has quit IRC | 03:09 | |
*** kd9261 has quit IRC | 03:32 | |
*** Binbin has joined #openstack-meeting | 03:48 | |
*** Binbin has quit IRC | 04:09 | |
*** dovetaildan has quit IRC | 04:43 | |
*** dovetaildan has joined #openstack-meeting | 04:44 | |
*** Binbin has joined #openstack-meeting | 05:14 | |
*** Binbin has quit IRC | 05:48 | |
*** Binbin has joined #openstack-meeting | 05:57 | |
*** Binbin has quit IRC | 06:32 | |
*** Binbin has joined #openstack-meeting | 06:35 | |
*** Binbin has quit IRC | 06:42 | |
*** mancdaz has quit IRC | 08:47 | |
*** Binbin has joined #openstack-meeting | 08:49 | |
*** mancdaz has joined #openstack-meeting | 08:49 | |
*** mancdaz has quit IRC | 08:54 | |
*** mancdaz has joined #openstack-meeting | 08:55 | |
*** adjohn has quit IRC | 09:03 | |
*** Binbin has quit IRC | 09:22 | |
*** zul has joined #openstack-meeting | 10:14 | |
*** JordanRinke has quit IRC | 11:32 | |
*** JordanRinke has joined #openstack-meeting | 11:37 | |
*** Binbin has joined #openstack-meeting | 11:54 | |
*** dwcramer has joined #openstack-meeting | 12:00 | |
*** soren has quit IRC | 12:06 | |
*** dprince has joined #openstack-meeting | 12:11 | |
*** soren has joined #openstack-meeting | 12:13 | |
*** dwcramer has quit IRC | 12:31 | |
*** Binbin has quit IRC | 12:49 | |
*** Binbin has joined #openstack-meeting | 13:20 | |
*** mattray has joined #openstack-meeting | 13:29 | |
*** edconzel has joined #openstack-meeting | 13:46 | |
*** med_out has quit IRC | 13:50 | |
*** Binbin has quit IRC | 13:56 | |
*** medberry has joined #openstack-meeting | 14:11 | |
*** medberry has joined #openstack-meeting | 14:11 | |
*** rnirmal has joined #openstack-meeting | 14:15 | |
*** medberry has quit IRC | 14:19 | |
*** dwcramer has joined #openstack-meeting | 14:20 | |
*** medberry has joined #openstack-meeting | 14:21 | |
*** medberry has joined #openstack-meeting | 14:21 | |
*** johnpur has joined #openstack-meeting | 14:49 | |
*** jkoelker has joined #openstack-meeting | 14:52 | |
*** markwash has quit IRC | 15:10 | |
*** markwash has joined #openstack-meeting | 15:10 | |
*** dendrobates is now known as dendro-afk | 15:28 | |
*** dendro-afk is now known as dendrobates | 15:30 | |
*** troytoman-away is now known as troytoman | 15:33 | |
*** dendrobates is now known as dendro-afk | 15:58 | |
*** dendro-afk is now known as dendrobates | 15:58 | |
*** dendrobates is now known as dendro-afk | 16:11 | |
*** dendro-afk is now known as dendrobates | 16:18 | |
*** mattray has quit IRC | 16:27 | |
*** dendrobates is now known as dendro-afk | 16:36 | |
*** s1rp has quit IRC | 16:41 | |
*** mattray has joined #openstack-meeting | 17:05 | |
*** jakedahn has quit IRC | 17:37 | |
*** carlp has joined #openstack-meeting | 18:11 | |
*** dendro-afk is now known as dendrobates | 18:18 | |
*** Tv has joined #openstack-meeting | 18:20 | |
*** jakedahn has joined #openstack-meeting | 18:30 | |
*** dwcramer has quit IRC | 18:51 | |
*** zul has quit IRC | 19:22 | |
*** dprince has quit IRC | 19:43 | |
*** dendrobates is now known as dendro-afk | 20:01 | |
*** markvoelker has joined #openstack-meeting | 20:01 | |
*** AWR has joined #openstack-meeting | 20:02 | |
*** creiht has joined #openstack-meeting | 20:03 | |
termie | ttx: is there a public calendar i can subscribe to in gcal to see when the openstack meetings are? | 20:08 |
termie | notmyname, vishy: ^^ | 20:08 |
notmyname | ya. just a sec | 20:09 |
notmyname | http://tinyurl.com/openstack-meetings | 20:09 |
termie | yeah that gives me direct to an ics | 20:09 |
termie | but i'd rather just add the user it belongs to | 20:09 |
termie | maybe that will just work though | 20:10 |
*** dragondm has joined #openstack-meeting | 20:15 | |
termie | ya, that works | 20:15 |
termie | thanks | 20:15 |
mtaylor | termie: wow. that so didn't do anything for me on google calendar | 20:22 |
*** ohnoimdead has joined #openstack-meeting | 20:24 | |
termie | you have to get the acutal link | 20:33 |
termie | https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4%40group.calendar.google.com/public/basic.ics | 20:33 |
termie | mtaylor: ^ | 20:33 |
ttx | termie: interesting. I guess I should just give the full URL on the wikipage then | 20:40 |
*** bcwaldon has joined #openstack-meeting | 20:42 | |
*** dabo has joined #openstack-meeting | 20:48 | |
*** spectorclan_ has joined #openstack-meeting | 20:50 | |
*** vladimir3p has joined #openstack-meeting | 20:50 | |
*** alandman has joined #openstack-meeting | 20:55 | |
*** primeministerp has joined #openstack-meeting | 20:55 | |
notmyname | termie: PPB schedule https://www.google.com/calendar/ical/6i49nddt8eqqi1kv0uoc8noh94%40group.calendar.google.com/public/basic.ics | 20:56 |
ttx | mtaylor: just added the testing and CI meeting on it | 20:57 |
notmyname | ttx: so your calendar will now have the PPB meetings? | 20:58 |
ttx | notmyname: I gave jbryce admin access to the common "meeting" one | 20:58 |
notmyname | ah ok | 20:58 |
notmyname | thanks. | 20:58 |
notmyname | I much prefer only one calendar :-) | 20:58 |
ttx | it should be all set now | 20:58 |
ttx | mtaylor: I can give you access to it too, if you want to be able to change every week :) | 20:58 |
annegentle | ttx: can I have access? I am likely to change the doc/web team meeting to not-so-late | 20:59 |
*** jakedahn has quit IRC | 21:00 | |
*** Vek has joined #openstack-meeting | 21:00 | |
bcwaldon | annegentle: good idea. I was planning to attend but it totally slipped my mind | 21:00 |
*** mgius has joined #openstack-meeting | 21:00 | |
ttx | annegentle: sure -- it's a google calendar thing, if you have an account for that | 21:00 |
annegentle | ttx: coolio, anngentle@gmail.com | 21:01 |
*** jk0 has joined #openstack-meeting | 21:01 | |
*** danwent has joined #openstack-meeting | 21:01 | |
ttx | annegentle: should be ok now | 21:01 |
annegentle | thanks | 21:01 |
ttx | jaypipes, vishy: around ? | 21:02 |
*** dubs has joined #openstack-meeting | 21:02 | |
*** anotherjesse has joined #openstack-meeting | 21:02 | |
*** anotherjesse is now known as jesse_andrews | 21:02 | |
soren | annegentle: Really? Not annegentle@ (note the extra e)? | 21:02 |
ttx | vishy is traveling, I'll stand in for him as much as I can | 21:02 |
ttx | let's start | 21:03 |
ttx | #startmeeting | 21:03 |
openstack | Meeting started Tue Jun 7 21:03:08 2011 UTC. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:03 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 21:03 |
*** s1rp has joined #openstack-meeting | 21:03 | |
ttx | Welcome to the OpenStack team meeting... | 21:03 |
ttx | The agenda for today lives at: | 21:03 |
ttx | #link http://wiki.openstack.org/Meetings/TeamMeeting | 21:03 |
ttx | #topic Actions from previous meeting | 21:03 |
*** openstack changes topic to "Actions from previous meeting" | 21:03 | |
ttx | * ttx to create webnumbrs for Swift/Glance | 21:03 |
ttx | That was done at: | 21:03 |
ttx | #link http://wiki.openstack.org/releasestatus/swift.html | 21:03 |
ttx | #link http://wiki.openstack.org/releasestatus/glance.html | 21:04 |
ttx | not enough data to make it interesting yet | 21:04 |
*** byeager has joined #openstack-meeting | 21:04 | |
*** johan___ has joined #openstack-meeting | 21:04 | |
ttx | * dabo to make progress towards merging the nova python client library projects | 21:04 |
ttx | dabo: wanna talk about the status ? | 21:04 |
dabo | still in discussion with jacobian about adding committers from OpenStack to his project on GitHub | 21:05 |
jesse_andrews | dabo: what is the general though? | 21:05 |
dabo | he's all for combining | 21:05 |
jesse_andrews | dabo: as for which is the basis? | 21:05 |
ttx | jesse_andrews: his project | 21:05 |
dabo | we thought keeping it external would be a good check on the APIs | 21:06 |
*** ewanmellor has joined #openstack-meeting | 21:06 | |
dabo | but allow for OpenStack committers so that he's not a bottleneck | 21:06 |
ttx | dabo: cool | 21:06 |
dabo | he was +1 for that | 21:06 |
jesse_andrews | dabo: 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_andrews | to *MATCH* server extensions | 21:07 |
ttx | * mtaylor to set up a "functional testing" meeting to coordinate efforts | 21:07 |
ttx | mtaylor: around ? | 21:07 |
dabo | I only asked for sandy, jk0 and myself to be added. Let me know whatever github names you will also need as committers | 21:07 |
*** User432 has joined #openstack-meeting | 21:07 | |
ttx | That was done, meeting will be Tuesdays at 1900 UTC | 21:07 |
*** Tushar has joined #openstack-meeting | 21:07 | |
devcamcar | dabo: i'd like to be added as well | 21:07 |
bcwaldon | dabo: same here | 21:07 |
dabo | ok - send me your github names and I'll pass 'em along | 21:08 |
ttx | #topic Swift status | 21:08 |
*** openstack changes topic to "Swift status" | 21:08 | |
devcamcar | dabo: it's ... wait for it ............ devcamcar | 21:08 |
jk0 | dabo: jk0 :) | 21:08 |
*** somik has joined #openstack-meeting | 21:08 | |
devcamcar | :) | 21:08 |
dabo | whoda thunk it? | 21:08 |
ttx | notmyname: hi! Any updated plans for 1.4.1 ? | 21:08 |
*** masumotok has joined #openstack-meeting | 21:08 | |
notmyname | ttx: 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 week | 21:09 |
ttx | ack | 21:09 |
jesse_andrews | we don't need everyone to be added since we can just send pull requests right? | 21:09 |
ttx | We also need to decide in which PPA to put 1.4.0... | 21:09 |
pvo | jesse_andrews: the bottleneck was him incorporating those reqs. iirc. | 21:09 |
devcamcar | jesse_andrews: don't be a code blocker | 21:09 |
notmyname | ttx: indeed | 21:09 |
ttx | I think we need a PPA tracking the last Swift milestone/release, and one PPA tracking the last OpenStack coordinated release | 21:09 |
ttx | For Swift we already have a "Release PPA" with 1.3.0... That means two solutions: | 21:10 |
jesse_andrews | pvo: right - i'm just saying a few added people is good | 21:10 |
* pvo nods. | 21:10 | |
ttx | 1/ reuse the "Release PPA" for 1.4.0, and create a "OpenStack release PPA" with 1.3.0 | 21:10 |
ttx | 2/ create a "Milestone PPA" for 1.4.0 and leave the Release PPA as-is. | 21:10 |
dabo | jesse_andrews: pvo: yeah, as long as one of the stackers can merge into the project | 21:10 |
ttx | notmyname: Any preference ? | 21:10 |
notmyname | ttx: I prefer the first since our milestones are stable releases | 21:10 |
ttx | Right, I think (2) would confuse people around what is a Swift release | 21:10 |
jesse_andrews | dabo: did we setup a launchpad project to pull from the githubs? | 21:10 |
jesse_andrews | dabo: for ppa | 21:11 |
ttx | For (1) we would probably set up a common "OpenStack release PPA" containing all core projects | 21:11 |
dabo | jesse_andrews: not that I know of | 21:11 |
notmyname | yes | 21:11 |
ttx | #action ttx to push update of Swift release PPA to 1.4.0 and creation of a common OpenStack release PPA | 21:11 |
ttx | notmyname: Another question I had -- should we mark the fixed-in-1.4.0 bugs "FixReleased" ? Or wait for the common OpenStack release ? | 21:12 |
notmyname | they should be marked fixed released | 21:12 |
ttx | notmyname: ok, will make that happen, expectr bugnoise. | 21:12 |
ttx | notmyname: Other announcements or comments ? | 21:12 |
notmyname | nothing yet | 21:13 |
ttx | Questions for the Swift team ? | 21:13 |
ttx | jaypipes: around ? | 21:13 |
jaypipes | ttx: yes sir! | 21:13 |
ttx | #topic Glance status | 21:13 |
*** openstack changes topic to "Glance status" | 21:13 | |
ttx | jaypipes: hi! So same question for you... | 21:13 |
Vek | (of course he's round, he's a pipe!) | 21:13 |
* Vek ducks quickly | 21:13 | |
ttx | Do you think we should mark the fixed-in-diablo-1 bugs "FixReleased" ? Or leave them "FixCommitted" until the final release ? | 21:14 |
ttx | For Nova/Glance the latter probably makes more sense... | 21:14 |
*** antonyy has joined #openstack-meeting | 21:14 | |
jaypipes | bcwaldon 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 API | 21:14 |
jaypipes | ttx: fix committed is fine for now. | 21:14 |
johnpur | is keystone integration complete in d2 for glance? | 21:15 |
ttx | jaypipes: Plan at https://launchpad.net/glance/+milestone/diablo-2 looks good to me | 21:15 |
jaypipes | I've been working pretty hard on understanding Keystone and have been logging issues like crazy over on github... | 21:15 |
ttx | jaypipes: I assume status is up-to-date, i.e. most things are not started ? | 21:15 |
ttx | (still in investigation phase) | 21:15 |
jaypipes | the spec and API are changing quite rapidly, which makes things challenging, but making progress nonetheless | 21:15 |
jaypipes | ttx: exactly. | 21:15 |
devcamcar | folks on swift team, what is your timeframe for keystone support? | 21:15 |
ttx | jaypipes: Do you agree we should switch to milestone-proposed one day earlier, to give ~2 days for testing/fixes ? | 21:16 |
notmyname | devcamcar: diablo release, I believe | 21:16 |
jaypipes | ttx: expect bcwaldon and me to put some of those bps into a started status tomorrow through friday | 21:16 |
jaypipes | ttx: that's fine, sure | 21:16 |
jesse_andrews | notmyname: is gholt around? he has said he would be able to do a middleware pretty easy | 21:16 |
ttx | That means features for Glance diablo-2 must get merged before EOD June 27... Mark your calendars. | 21:16 |
jesse_andrews | notmyname: that does lazy provisioning | 21:16 |
jaypipes | ttx: yes, that is correct | 21:16 |
devcamcar | notmyname: know which milestone by chance? its a dependency for swift support in dashboard | 21:17 |
notmyname | devcamcar: jesse_andrews: I'll check with gholt | 21:17 |
devcamcar | thx | 21:17 |
jaypipes | ttx: that's it from me. | 21:17 |
jesse_andrews | devcamcar: 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 exists | 21:17 |
ttx | Any question about Glance ? | 21:17 |
jesse_andrews | jaypipes: the thought by D2 to have private image support? | 21:18 |
ttx | jesse_andrews: was that before or after beer oclock ? | 21:18 |
jesse_andrews | ttx: before | 21:18 |
jaypipes | jesse_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 |
jaypipes | jesse_andrews: but I think very doable for D3. | 21:18 |
ttx | other Glance questions before we move on to Nova ? | 21:19 |
jaypipes | jesse_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_andrews | jaypipes: cooleo | 21:19 |
*** ying has joined #openstack-meeting | 21:19 | |
ttx | #topic Nova status | 21:20 |
*** openstack changes topic to "Nova status" | 21:20 | |
ttx | unless vishy makes a surprise entry, I'll talk for him | 21:20 |
johnpur | vishy is turining japanese! | 21:20 |
ttx | The 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 |
pvo | johnpur: you really think so? | 21:21 |
pvo | ;p | 21:21 |
ttx | I've been busy sanitizing the diablo-2 plan, trying to see what should be reasonably done by then, and checking out assignees | 21:21 |
ttx | A bit scary with like 27 blueprints targeted | 21:21 |
ttx | See plan @ https://launchpad.net/nova/+milestone/diablo-2 | 21:21 |
ttx | I'm still missing some input, the plan should be finalized in the next days. | 21:21 |
jaypipes | ttx: markwash told me he'd pick up 10 or 12 blueprints. | 21:22 |
ttx | If 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 dendrobates | 21:22 | |
pvo | ttx: I'll make sure I get our plans to you soon. | 21:22 |
ttx | Questions ? | 21:22 |
jesse_andrews | ttx: my assumption was the "low" ones were icing on the cake | 21:22 |
ttx | jesse_andrews: yes -- we could actually keep them untargeted and target them retrospectively when they land | 21:23 |
tr3buchet | seems cleaner that way | 21:23 |
jesse_andrews | pvo / ozone folks - how risky is multi-nic landing? | 21:24 |
ttx | jesse_andrews: I'll give that a thought. They were originally targeted by Vish, will talk to him | 21:24 |
pvo | jesse_andrews: I know the tests are being cleaned up now. | 21:24 |
jesse_andrews | pvo: nice :) | 21:24 |
tr3buchet | jesse_andrews: as to multi-nic it depends on review respoonse | 21:24 |
ttx | #action ttx to consider untargeting/retrotarget Low specs to decrease noise | 21:25 |
ttx | also, congrats to nova-core for decreasing the review queue to 12 open reviews | 21:26 |
ttx | anything else on Nova ? | 21:26 |
ttx | ah! down to 10 now. | 21:26 |
annegentle | wow, nice job team | 21:27 |
tr3buchet | which means i surely need to merge trunk again | 21:27 |
tr3buchet | ;) | 21:27 |
devcamcar | hah, yea | 21:27 |
jaypipes | hehe | 21:27 |
ttx | #topic Doc status | 21:27 |
*** openstack changes topic to "Doc status" | 21:27 | |
ttx | annegentle: floor is yours. | 21:27 |
annegentle | Thanks. We held our first doc/web meeting last night, and went through goals for the meeting and team. | 21:27 |
annegentle | I have a fresh perspective on and respect for the talents inherent in running meetings on IRC. :) | 21:27 |
annegentle | A couple of items of interest to the larger team: | 21:27 |
ttx | heh | 21:27 |
annegentle | toddmorey 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 |
johnpur | annegentle: no doubt you are awesome! | 21:28 |
annegentle | toddmorey has also implemented the site in Silverstripe which should enable more contributors | 21:28 |
ttx | annegentle: coolio | 21:28 |
annegentle | The 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-meeting | 21:29 | |
annegentle | It'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 |
annegentle | The next set of CC-licensed contributions are from CSS Corp Open Source Services, hoping to get those in next week. | 21:29 |
annegentle | Lastly, doc builds are now happening automatically when merge props are reviewed/accepted. | 21:30 |
jkoelker | inetrY6o | 21:30 |
annegentle | I'll probably move the time to North America daytime, but we'll continue to meet monthly. | 21:30 |
ttx | annegentle: ok | 21:31 |
annegentle | Any doc/website questions? | 21:31 |
bcwaldon | jkoelker: it showed up as all *'s to me | 21:31 |
tr3buchet | :) | 21:31 |
jkoelker | rigggghhht | 21:31 |
jkoelker | focus follows mouse is bad | 21:31 |
Vek | now there's a religious war! | 21:31 |
* tr3buchet puts on his wizard hat and robe | 21:32 | |
ttx | annegentle: apparently not. Thanks for that update | 21:32 |
ttx | #topic Open discussion | 21:32 |
*** openstack changes topic to "Open discussion" | 21:32 | |
johnpur | jkoelker: 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 review | 21:32 |
ttx | johnpur: especially since he uses SecurID | 21:32 |
johnpur | spectorclan: how firm is this location? | 21:33 |
carlp | quick question: is that 1900UTC meeting on Tuesdays for the larger distributed automated testing environment using jenkins? | 21:33 |
ttx | spectorclan: oh, that's very new | 21:33 |
spectorclan_ | Pretty firm - not many places available and this is a popular spot; hotel was just redone and great location | 21:33 |
Vek | and right on the green line | 21:34 |
notmyname | devcamcar: jesse_andrews: https://github.com/rackspace/keystone/blob/master/docs/swift-quick-start.txt | 21:34 |
* ttx looks it up | 21:34 | |
notmyname | see the bottom of that page for keystone/swift integration notes | 21:34 |
johnpur | spectorclan: can we open the floor to suggestions about 'e' names for the next release? | 21:34 |
eday | spectorclan_: are those dates+boston firm for sure? (even if hotel changes) | 21:34 |
jesse_andrews | notmyname: NICE | 21:34 |
spectorclan_ | Yes, dates are firm | 21:34 |
notmyname | jesse_andrews: all gholt :-) | 21:34 |
spectorclan_ | ttx: those are the dates you gave me, correct? | 21:35 |
jesse_andrews | go gholt, it is your birthday! | 21:35 |
* ttx doublechecks | 21:35 | |
devcamcar | notmyname, gholt: word | 21:35 |
ttx | spectorclan: yes! | 21:35 |
*** medberry is now known as med_out | 21:36 | |
ttx | johnpur: let's keep that for the next meeting | 21:36 |
spectorclan_ | Any questions on the CLA process I started today? | 21:36 |
ttx | though suggestions are ok :) | 21:36 |
johnpur | ttx: ok, i am just excited about what the next name will be! | 21:37 |
notmyname | ttx: johnpur: https://secure.wikimedia.org/wikipedia/en/wiki/List_of_cities_in_Texas#E | 21:37 |
*** AlexNeef has joined #openstack-meeting | 21:37 | |
eday | http://massachusetts.hometownlocator.com/cities/listcitiesalpha,alpha,e.cfm if we want a 'E' name near boston :) | 21:37 |
creiht | Evil | 21:37 |
johnpur | spectorclan: the cla process looks good to me. | 21:37 |
spectorclan_ | ttx: I thought E comes from Massachusetts and not Texas? | 21:37 |
ttx | notmyname: we need to pik somewhere in MA, preferably in Boston area | 21:37 |
carlp | All I can think of is Easton | 21:38 |
Vek | everett? (doubt I have the right spelling) | 21:38 |
johnpur | i bet we have a lot of folks in the NE that can help with naming! | 21:38 |
jesse_andrews | Edgeworth | 21:38 |
spectorclan_ | Essex | 21:38 |
Vek | there's one I never heard of. | 21:38 |
*** ramd has joined #openstack-meeting | 21:38 | |
johnpur | primeministerp: around? | 21:39 |
spectorclan_ | There is a Mount Everett | 21:39 |
pvo | heh. Egypt. | 21:39 |
ttx | "Everett" | 21:39 |
*** SumitNaiksatam has joined #openstack-meeting | 21:39 | |
spectorclan_ | Eagle Hill River | 21:40 |
creiht | of course if we use the Texas form of the word close, you could include several states in the search :) | 21:40 |
ttx | spectorclan: multiple words are not ok | 21:40 |
Vek | haha :) | 21:40 |
alandman | johnpur: primeminsterp's not around | 21:40 |
johnpur | ttx: as a Seattle native... Everett is west coast | 21:40 |
ttx | johnpur: http://en.wikipedia.org/wiki/Everett,_Massachusetts | 21:40 |
ttx | not that one ^ | 21:40 |
ttx | Can be a city or a county | 21:41 |
ttx | see http://wiki.openstack.org/ReleaseNaming | 21:41 |
johnpur | alandman: have opinion on 'e' names close to Boston? | 21:41 |
ttx | MA is small, that won't leave so many options | 21:41 |
spectorclan_ | Essex is the only county | 21:41 |
ttx | spectorclan: yep | 21:42 |
notmyname | Eliot is a Boston suburb | 21:42 |
ttx | that could work. | 21:43 |
alandman | notmyname: Where is Eliot | 21:43 |
creiht | There is an Eden, Vermont | 21:43 |
notmyname | alandman: http://massachusetts.hometownlocator.com/ma/middlesex/eliot.cfm | 21:43 |
notmyname | creiht: and eden texas :-) | 21:43 |
creiht | indeed | 21:43 |
Vek | hmmm... | 21:44 |
tr3buchet | Edinburgh, UK | 21:44 |
alandman | notmyname: Noone I know that lives here would ever use that name for that area | 21:44 |
Vek | Eastham, Easthampton, Easton, Edgartown, Egremont, Erving, Essex, and Everett are all the single-word E names for Massachusetts. | 21:44 |
notmyname | alandman: "suburb of Boston"? just looks close on the map to me | 21:44 |
Vek | (municipality names) | 21:45 |
alandman | notmyname: People would call that area Netwon, from the town | 21:45 |
ttx | feel free to edit the wiki with your preferred candidates | 21:45 |
Vek | there used to be an Enfield, MA... | 21:45 |
ttx | #endmeeting | 21:45 |
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 21:45 | |
openstack | Meeting ended Tue Jun 7 21:45:50 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:45 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-21.03.html | 21:45 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-21.03.txt | 21:45 |
openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-21.03.log.html | 21:45 |
*** spectorclan_ has left #openstack-meeting | 21:46 | |
*** jk0 has left #openstack-meeting | 21:46 | |
Vek | http://en.wikipedia.org/wiki/List_of_municipalities_in_Massachusetts | 21:46 |
*** mgius has left #openstack-meeting | 21:46 | |
*** jesse_andrews has quit IRC | 21:47 | |
Vek | East Boston has the nickname "Eastie" | 21:48 |
soren | "East Boston" sounds great. | 21:48 |
Vek | two words, though. | 21:48 |
soren | EastBoston. | 21:48 |
soren | Win. | 21:48 |
ttx | soren: East%20Boston doesn't, though. | 21:48 |
Vek | heh :) | 21:49 |
*** salv-orlando has joined #openstack-meeting | 21:51 | |
carlp | There are a lot of "East %" locations in MA | 21:51 |
*** midodan has joined #openstack-meeting | 21:51 | |
*** bcwaldon has left #openstack-meeting | 21:52 | |
*** masumotok has quit IRC | 21:53 | |
*** dendrobates is now known as dendro-afk | 21:55 | |
*** dendro-afk is now known as dendrobates | 21:55 | |
*** eperdomo has joined #openstack-meeting | 21:55 | |
*** ewanmellor has quit IRC | 21:56 | |
*** johnpur has quit IRC | 21:56 | |
*** Vek has left #openstack-meeting | 21:56 | |
*** alekibango has joined #openstack-meeting | 21:59 | |
*** rnirmal has quit IRC | 21:59 | |
dendrobates | o/ | 22:00 |
danwent | hello | 22:00 |
markvoelker | o/ | 22:00 |
danwent | look, real internet connectivity :) | 22:00 |
AlexNeef | hi | 22:00 |
somik | hello all | 22:01 |
danwent | FYI: brad from nicira is afk right now | 22:01 |
dendrobates | lets wait a few minutes for people to show up | 22:02 |
danwent | sure, much quieter than usual today. | 22:02 |
salv-orlando | Hi everybody! | 22:02 |
midodan | hi guys | 22:02 |
AWR | hay!! | 22:02 |
*** romain_lenglet has joined #openstack-meeting | 22:03 | |
alekibango | hello :) | 22:03 |
salv-orlando | I see a few new names today (or just the usual ones with different nicks)... | 22:03 |
AWR | how is everyone? | 22:03 |
danwent | great :) | 22:03 |
AlexNeef | good | 22:03 |
SumitNaiksatam | hello | 22:04 |
carlp | not too bad | 22:04 |
danwent | salv: agreed. if you're new, care to introduce yourself? | 22:04 |
AWR | ill start | 22:04 |
dendrobates | or if you changed your nick, tell us who you are? | 22:04 |
AWR | hi im AWR ;) | 22:04 |
danwent | :) | 22:04 |
AWR | im semi new to openstack | 22:05 |
AWR | working on setting up now | 22:05 |
AWR | and figured i woudl see what the team meetings were like | 22:05 |
danwent | ah, great. We're the "NetStack" team, focused on networking for openstack. | 22:06 |
*** mattray has quit IRC | 22:06 | |
danwent | still in its very early stages, not an official project yet. | 22:06 |
dendrobates | AWR: the main openstack meeting just ended | 22:06 |
dendrobates | but this one is more exciting anyway | 22:07 |
byeager | I am not new, but I haven't been around much lately, trying to get plugged back in... | 22:07 |
dendrobates | hey blake | 22:07 |
dendrobates | welcome back | 22:07 |
danwent | hi blake | 22:07 |
byeager | thanks rick, good to be back around | 22:07 |
dendrobates | shall we start? | 22:08 |
AWR | t dendrobates: i know, i was silent through it since i really didnt have anything to ad | 22:08 |
carlp | sure! | 22:08 |
danwent | i say we're good to go | 22:08 |
dendrobates | #startmeeting | 22:08 |
openstack | Meeting started Tue Jun 7 22:08:31 2011 UTC. The chair is dendrobates. Information about MeetBot at http://wiki.debian.org/MeetBot. | 22:08 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 22:08 |
dendrobates | #topic project update | 22:08 |
*** openstack changes topic to "project update" | 22:08 | |
dendrobates | I believe some code has been pushed by Rackspace | 22:09 |
dendrobates | Is anyone here to talk about it? | 22:09 |
*** jakedahn has joined #openstack-meeting | 22:09 | |
danwent | to what project? | 22:09 |
danwent | is this the quantum extensions stuff? | 22:09 |
dendrobates | danwent: the quantum stuff | 22:09 |
dendrobates | yes | 22:09 |
somik | I just saw a merge proposal for extensions | 22:09 |
danwent | Ok, was going to bring that up in the quantum section. | 22:09 |
danwent | or perhaps we're there already :) ? | 22:09 |
dendrobates | sure, go ahead | 22:10 |
danwent | cool | 22:10 |
danwent | still 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/quantum | 22:10 |
danwent | this does not include the extensions. | 22:10 |
danwent | includes 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 |
danwent | please see the README | 22:10 |
danwent | no packaging for now. | 22:10 |
danwent | no tenant auth. no GUI | 22:11 |
danwent | anyone who would like to see such things, let me know ;) | 22:11 |
salv-orlando | do we have any form of integration with nova? or a tweaked version of nova? | 22:11 |
danwent | Running with OVS plugin doesn't require a tweaked version of nova, standalone nova will work. | 22:11 |
danwent | I think the README for the OVS plugin describes that. | 22:11 |
salv-orlando | good | 22:12 |
danwent | working with libvirt will require some tweaks. | 22:12 |
carlp | Can the OVS plugin be run on KVM? | 22:12 |
danwent | to nova, we'll probably post a nova branch to do that soon. | 22:12 |
carlp | danwent: can we talk about that later? | 22:12 |
danwent | carlp: sure | 22:12 |
carlp | danwent: I'm interested to see what I can help contribute | 22:12 |
*** edconzel has quit IRC | 22:12 | |
danwent | carlp: basic point is that you need to generate the libvirt XML a little differently. | 22:12 |
danwent | carlp: sounds good. | 22:12 |
dendrobates | carlp: Cisco is interested in libvirt/kvm support as well | 22:13 |
danwent | What dendrobates was mentioning is that there was a recent merge request from santhosh: https://code.launchpad.net/~santhom/network-service/quantum_framework/+merge/63711 | 22:13 |
danwent | this arrived this morning. I don't now if anyone has had time to take a look yet (we haven't). | 22:13 |
dendrobates | is troytoman around? | 22:13 |
salv-orlando | I had a quick look at that | 22:13 |
carlp | dendrobates: good to know | 22:13 |
danwent | it apparently includes code from nova on extensions, plus some unit test improvements, plus some pep8 fixes. | 22:14 |
dendrobates | I looked at it, and am gettng a few other cisco devs on it. | 22:14 |
danwent | I suspect most of the interest will be with respect to the exstensions. | 22:14 |
danwent | dendrobates: great. | 22:14 |
salv-orlando | yeah the extension model allows for defining new resources, new methods and new methods on existing resources | 22:14 |
danwent | if the extension stuff is contentious, we'll probably try to split it out from the unit test + pep8 stuff. | 22:14 |
danwent | as that seems pretty vanilla. | 22:15 |
dendrobates | danwent: that is a good idea | 22:15 |
danwent | I know other people had registered interest in how extensions work, so I want to make sure there's time for review. | 22:15 |
danwent | is santhosh around? | 22:15 |
dendrobates | hello rackspace? | 22:16 |
danwent | ok, i'll assume not, troy or any other rackers? | 22:16 |
dendrobates | we will have to follow up with them in email. | 22:16 |
danwent | agreed. | 22:16 |
ying | danwent: yes, I'm interested. Just briefly looked it today and will follup with emails | 22:16 |
danwent | ying: I figured :) sounds good. | 22:17 |
danwent | in 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 |
danwent | plan to have something by end of this week. | 22:17 |
*** creiht has left #openstack-meeting | 22:18 | |
danwent | Overall, quantum should be in a place were other people can start playing with it. | 22:18 |
danwent | things like donabe or other services should be able to start developing against it. | 22:18 |
dendrobates | great | 22:18 |
salv-orlando | danwent: the doc would be great. let me know if you want help preparing/reviewing it | 22:18 |
danwent | we still need more effort around system test, docs, etc. | 22:18 |
danwent | salv: yes, definitely, everyone should collaborate on it. agreed. | 22:19 |
salv-orlando | and 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 IRC | 22:19 | |
dendrobates | salv-orlando: sure, Dan are you done? We could do it now. | 22:19 |
salv-orlando | * current trunk has pep8 errors... | 22:20 |
danwent | salv: Yes, agreed. | 22:20 |
dendrobates | #topic Netstack review process | 22:20 |
*** openstack changes topic to "Netstack review process" | 22:20 | |
danwent | salv: 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 |
danwent | dendrobates: yes, done :) | 22:21 |
dendrobates | Is there any reason that we should not follow the openstack core processes? | 22:21 |
danwent | I think this just comes down to defining the "core" devs. | 22:21 |
salv-orlando | not from me. I think we just need to define the "netstack-core" now | 22:21 |
danwent | but i don't see a reason to diverge from opestack common practice. | 22:22 |
dendrobates | I recieved emails from only 2 people about core dev status | 22:22 |
dendrobates | Why don't I draft a core-team list and we can review it at the next meeting | 22:22 |
dendrobates | before I create it | 22:23 |
salv-orlando | dendrobates: agreed | 22:23 |
danwent | I'm fine with that. | 22:23 |
dendrobates | if anyone wants to be sure to be on it, please send me an email | 22:23 |
salv-orlando | Is there a "python reviews for dummies" manual available somewhere :-) | 22:24 |
salv-orlando | ? | 22:24 |
somik | sure.. we havesome code and as people start creating patches and submitting merge proposals we can expand the core. | 22:24 |
danwent | dendorbates: as part of that, can you put together pointers to the materials used by nova (style guides, etc?) | 22:24 |
troytoman | sorry guys ... i'm a bit late ... firefighting day for me! | 22:24 |
dendrobates | It is just one line. " be fascist about pep8" | 22:24 |
danwent | :) | 22:24 |
dendrobates | danwent: yes I can | 22:24 |
alekibango | dendrobates: fascism = merge of corporations + government.. we maybe should use the word as it deserve | 22:25 |
dendrobates | one place tha tnova has fallen down, IMHO , is with naming standards. I suggest we take a stab at that too | 22:25 |
danwent | dendrobates: in what sense? | 22:25 |
danwent | variables? | 22:25 |
dendrobates | danwent: yes | 22:26 |
danwent | k | 22:26 |
dendrobates | the goal is ease of understanding and a quick path to contribution | 22:26 |
danwent | ok, open discuss? | 22:27 |
dendrobates | #topic open discussion | 22:27 |
*** openstack changes topic to "open discussion" | 22:27 | |
salv-orlando | since troy is here now, we can probably have an update on melange | 22:28 |
dendrobates | the dmtf has some standards for defining network parameters that is being included with OVF 2.0 | 22:28 |
troytoman | sure. 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 |
dendrobates | If they are good, I suggest we standardize on them | 22:29 |
danwent | dendrobates: is there a link available yet? I'm unfamiliar with this. | 22:29 |
troytoman | Otherwise, we are waiting for multi-nic and network refactoring to figure out how to integrate melange into Nova | 22:29 |
dendrobates | danwent: It might still be in the working group | 22:30 |
somik | I think OVF 2.0 is still under discussion | 22:30 |
danwent | dendrobates: should we consider trying to be part of the discussion? | 22:30 |
dendrobates | danwent: I think it is too late, but we should at least look at it and comment | 22:31 |
danwent | k | 22:31 |
salv-orlando | troytoman: I was looking at the IPAM protocol proposal on github. | 22:31 |
carlp | troytoman: Let me know when/if you would like us to look that over too | 22:31 |
Tv | salv-orlando: url please? | 22:31 |
salv-orlando | Does this protocol replaces normal DHCP discovery/request/offer process? | 22:31 |
salv-orlando | tv: I think is this: https://github.com/tv42/melange-discovery/blob/master/melange-discovery.rst | 22:33 |
troytoman | slv-orlando: the github proposal on the protocol is being done by tv | 22:33 |
salv-orlando | sorry I'm not at my work laptop | 22:33 |
troytoman | my team has been focused on the address tracking part | 22:33 |
Tv | ok just wanted to know if that's what you're talking about | 22:33 |
salv-orlando | troytoman: I see. Apologies for misunderstanding... | 22:33 |
Tv | salv-orlando: that is intended to look like dhcp to the vm | 22:33 |
troytoman | carlp: when we have the integration proposal together, I'll send it out more broadly. probably before end of the week | 22:33 |
carlp | troytoman: cool, thanks | 22:33 |
Tv | salv-orlando: while delegating all the decision making to the melange ipam | 22:34 |
salv-orlando | tv: that means, for instance, VM sends DHCP request, and it is then translated into Melange IPAM message? | 22:35 |
Tv | salv-orlando: roughly, yes | 22:35 |
danwent | one 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 |
Tv | danwent: private networks are basically L2 without IPAM services, so no | 22:35 |
danwent | though it seems like one valid approach if you did not care about that use case. | 22:35 |
Tv | danwent: i'd expect those interfaces are not subject to this processing at all | 22:35 |
Tv | danwent: my thinking is, it's the customer's L2, they run DHCP if they want etc, *nothing* should touch the packets | 22:36 |
danwent | OK, so this would be enabled only for certain interfaces. | 22:36 |
Tv | danwent: including the host firewall | 22:36 |
danwent | Ok, that seems reasonable :) | 22:36 |
Tv | danwent: more like, your VPC L2 networks are separate vifs | 22:36 |
Tv | (want to run non-IP in your private L2? go right ahead!) | 22:37 |
Tv | i guess the spec could talk of VPCs | 22:37 |
salv-orlando | tv: 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 |
Tv | salv-orlando: i haven't considered that use case | 22:38 |
Tv | salv-orlando: that would be.. "interesting" for the ipam component, i guess | 22:38 |
Tv | salv-orlando: like, completely different from its primary purpose of managing the outside-visible addresses | 22:39 |
Tv | salv-orlando: i'd rather ignore that for now, say that you manage the LAN as you wish | 22:39 |
danwent | Yeah, 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-orlando | tv: agreed. | 22:39 |
danwent | so is IPAM only about managing public IPs? | 22:39 |
Tv | danwent: i think of VPCs as something the cloud provider should not touch, at all | 22:40 |
Tv | there may be other opinions on that | 22:40 |
danwent | Tv: sure. don't want to derail the who meeting on this. we can move this offline :) | 22:40 |
Tv | danwent: but i wouldn't say IPAM is only about "public" IPs.. as in, it would be useful for managing 10.x.x.x too | 22:40 |
Tv | danwent: yes | 22:40 |
danwent | Tv: agreed. | 22:40 |
salv-orlando | I 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 |
Tv | salv-orlando: sure, i'm just inclined to postpone that; the code should be reusable, but i'd rather focus on one thing at a time | 22:41 |
salv-orlando | tv: I agree with you. I don't want to push this :-) | 22:41 |
troytoman | salv-orlando: not in scope for the initial release. but, it could evolve that way | 22:42 |
Tv | and that brings harder concepts like realms (whose 10.x.x.x are you talking about) etc | 22:42 |
troytoman | also, we are setting it up to be able to track both private and public IPs. Also, track NAT relationships between the two | 22:42 |
Tv | it'd be nice to find out that that wasn't ultimately needed at all ;) | 22:42 |
danwent | ok, any other open discussion? | 22:44 |
dendrobates | not from me | 22:44 |
salv-orlando | A couple of bits on Quantum API: | 22:44 |
Tv | i have a question about quantum | 22:44 |
* Tv waits for salv-orlando | 22:44 | |
salv-orlando | go ahead tv | 22:44 |
danwent | Tv: shoot | 22:44 |
Tv | hah! | 22:44 |
Tv | ok so.. vlans? | 22:44 |
salv-orlando | I registered a blueprint today | 22:45 |
Tv | will quantum have other means of identifying networks on the physical network that connects the hypervisor hosts than vlans? | 22:45 |
danwent | Tv: definitely. | 22:45 |
Tv | danwent: i'd be interested in more detail | 22:45 |
danwent | Tv: plugins should be able to use any type of mechanism for L2 segmentation. | 22:45 |
danwent | Tv: openvswitch for example can do cool things with L2-in-L3 tunneling. | 22:45 |
danwent | Tv: happy to talk more about this, but don't want to commandeer the meeting. | 22:46 |
Tv | i see just one openvswitch plugin that seems to have vlans pretty tied into the core of it | 22:46 |
ramd | salv: Are you planning the "VLAN manager port" as default-plugin? | 22:46 |
Tv | danwent: i'd very much like to know more, after the meeting | 22:46 |
danwent | Tv: yes, for the experimental plugin we just wanted to get something out the door, vlans are by far the easiest thing. | 22:46 |
salv-orlando | ramd: no I was just thinking it would be good to have it | 22:46 |
danwent | Tv: shoot me an email and we can chat. | 22:48 |
ramd | sure. I agree with dan; for quantum api level physical segmentation scheme could be anything | 22:48 |
ramd | for starters it happens to be vlan | 22:48 |
danwent | that was the whole goal of having it be a logical API. | 22:48 |
danwent | any technology could be behind it. | 22:48 |
salv-orlando | I have registered a blueprint for a porting to quantum of the 'traditional' nova's vlan manager over linux bridge. | 22:48 |
salv-orlando | I thought it would be good to have it as well. | 22:49 |
ramd | salv: +1 | 22:49 |
ramd | In the design summit we also talked about retaining current network-manager as well | 22:50 |
dendrobates | anything else? | 22:50 |
Tv | danwent: 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 |
danwent | Tv: my guess is that we will make the openvswitch plugin be able to handle both vlans and other segmentation mechanisms | 22:51 |
danwent | Tv: that is, config options rather than separate plugins. | 22:51 |
dendrobates | Tv: do you mean should openvswitch own the vlan namespace? | 22:52 |
Tv | dendrobates: i don't mean it should; i mean that what it looks like now | 22:52 |
danwent | Tv: you'll need some plugin logic that decide who owns vlans. | 22:52 |
dendrobates | but that multiple plugins could perform that function | 22:53 |
Tv | danwent: ok so code in the most essential alternative implementations, that'll work | 22:53 |
somik | dendrobates: correct | 22:53 |
Tv | dendrobates: no you're thinking this kinda the other way | 22:53 |
Tv | dendrobates: i want to have openvswitch-but-not-vlan | 22:53 |
dendrobates | ah | 22:53 |
danwent | Tv: people can definitely write other plugins that use openvswitch as well. | 22:53 |
*** jkoelker has quit IRC | 22:53 | |
danwent | or they can extend the openvswitch plugin, whichever makes sense. | 22:54 |
danwent | Some people have already contacted us about building a plugin that extends the OVS plugin as a python class. | 22:54 |
danwent | you can also introduce new things into the data model, etc. code sharing is a beautiful thing :) | 22:55 |
Tv | danwent: 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 plugin | 22:55 |
danwent | Tv: K. I think either approach would work. Happy to chat more with you. | 22:55 |
Tv | but yeah, good to hear that the non-vlan case is still in general awareness | 22:55 |
danwent | Tv: k | 22:56 |
dendrobates | I have another question, but it can wait until next time | 22:56 |
danwent | wow, 4pm already :) | 22:57 |
salv-orlando | I too have a question on Quantum API but will send an email | 22:57 |
dendrobates | 6pm for some and later for others | 22:57 |
danwent | haha :) | 22:57 |
markvoelker | 7 for us east coasters =) | 22:57 |
salv-orlando | make it midnight for me :-) | 22:57 |
dendrobates | #endmeeting | 22:57 |
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 22:57 | |
danwent | ok, i get it :) | 22:57 |
openstack | Meeting ended Tue Jun 7 22:57:45 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:57 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-22.08.html | 22:57 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-22.08.txt | 22:57 |
openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-06-07-22.08.log.html | 22:57 |
ramd | quit | 22:57 |
*** ramd has quit IRC | 22:58 | |
somik | have a good one everybody! | 22:58 |
salv-orlando | bye, talk to you next tuesday! | 22:58 |
dendrobates | bye | 22:58 |
*** AlexNeef has quit IRC | 22:58 | |
*** markvoelker has quit IRC | 22:58 | |
danwent | see you all! | 22:58 |
*** salv-orlando has left #openstack-meeting | 22:58 | |
*** ramd_ has joined #openstack-meeting | 22:58 | |
*** SumitNaiksatam has quit IRC | 22:58 | |
*** ying has quit IRC | 22:58 | |
*** ramd_ has quit IRC | 22:58 | |
carlp | danwent: still there? | 22:58 |
danwent | btw, carlp, I think you wanted to follow-up as well. send me email if you like. | 22:58 |
danwent | haha :) | 22:58 |
carlp | OK, I think I have your address somewhere.... | 22:58 |
carlp | yes, yes I do :) | 22:59 |
danwent | dan@nicira.com | 22:59 |
danwent | I've actually got to run to another meeting. Is it OK to talk later? | 22:59 |
*** danwent has left #openstack-meeting | 23:00 | |
carlp | yeah, no problem | 23:00 |
*** agarwalla has quit IRC | 23:00 | |
*** antonyy has quit IRC | 23:07 | |
*** troytoman is now known as troytoman-away | 23:13 | |
*** toddmorey has joined #openstack-meeting | 23:15 | |
*** dendrobates is now known as dendro-afk | 23:15 | |
*** toddmorey has quit IRC | 23:19 | |
*** dragondm has quit IRC | 23:22 | |
*** toddmorey has joined #openstack-meeting | 23:25 | |
*** dwcramer has joined #openstack-meeting | 23:37 | |
*** somik has quit IRC | 23:41 | |
*** Tushar has quit IRC | 23:42 | |
*** ohnoimdead has quit IRC | 23:49 | |
*** Tv has left #openstack-meeting | 23:57 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!