Monday, 2011-07-11

*** glenc has quit IRC00:35
*** glenc has joined #openstack-meeting00:36
*** ryu_ishimoto has joined #openstack-meeting01:16
*** ryu_ishimoto has quit IRC01:33
*** ryu_ishimoto has joined #openstack-meeting02:25
*** Dans has joined #openstack-meeting02:42
*** ryu_ishimoto has left #openstack-meeting02:43
*** Dans has quit IRC02:53
*** deshantm has quit IRC09:40
*** deshantm has joined #openstack-meeting09:48
*** johnpur has joined #openstack-meeting11:44
*** Binbin has joined #openstack-meeting11:53
*** robc has joined #openstack-meeting12:03
*** sandywalsh has joined #openstack-meeting12:14
*** whitt__ has joined #openstack-meeting12:28
*** Binbin has quit IRC12:33
*** cynb has joined #openstack-meeting12:34
*** Binbin has joined #openstack-meeting12:47
*** robc has left #openstack-meeting12:55
*** med_out is now known as medberry13:16
*** dendro-afk is now known as dendrobates13:30
*** Guest44632 has joined #openstack-meeting13:38
*** Guest44632 has left #openstack-meeting13:39
*** edconzel has joined #openstack-meeting13:56
*** edconzel has quit IRC14:00
*** edconzel has joined #openstack-meeting14:06
*** markvoelker has joined #openstack-meeting14:08
*** markvoelker has left #openstack-meeting14:14
*** dendrobates is now known as dendro-afk14:18
*** Binbin has quit IRC14:23
*** jkoelker has joined #openstack-meeting14:33
*** dragondm has joined #openstack-meeting15:09
*** dprince has joined #openstack-meeting15:19
*** rnirmal has joined #openstack-meeting15:29
*** heckj has joined #openstack-meeting15:31
*** jp_at_hp has joined #openstack-meeting16:21
*** jp_at_hp has left #openstack-meeting16:21
*** ohnoimdead has joined #openstack-meeting16:27
*** blakeyeager has joined #openstack-meeting16:28
*** msinhore has joined #openstack-meeting16:57
*** joearnold has joined #openstack-meeting17:06
*** troytoman-away is now known as troytoman17:06
*** msinhore has quit IRC17:17
*** msinhore has joined #openstack-meeting17:34
*** vladimir3p has joined #openstack-meeting17:43
*** joearnold has quit IRC17:48
*** joearnold has joined #openstack-meeting17:49
*** rupakg has joined #openstack-meeting17:52
*** rupakg has left #openstack-meeting17:52
*** msinhore has quit IRC18:01
*** mattray1 has joined #openstack-meeting18:15
*** adjohn has joined #openstack-meeting18:17
*** mattray1 is now known as mattray18:19
*** mattray has quit IRC18:19
*** mattray has joined #openstack-meeting18:19
*** adjohn has quit IRC18:42
*** adjohn has joined #openstack-meeting18:44
*** mattray1 has joined #openstack-meeting19:04
*** mattray has quit IRC19:08
*** dwcramer has joined #openstack-meeting19:16
*** jeblair has joined #openstack-meeting19:25
*** msinhore has joined #openstack-meeting19:26
*** dprince has quit IRC19:27
*** toddmorey has joined #openstack-meeting19:33
*** mattray1 is now known as mattray19:34
*** mattray has joined #openstack-meeting19:34
*** spectorclan_ has joined #openstack-meeting19:45
*** adjohn has quit IRC19:52
*** mencken has joined #openstack-meeting20:00
annegentlehello all20:01
toddmoreyhello!20:01
annegentleo/20:01
annegentleabout to get started if we're ready20:01
deshantmhello20:01
spectorclan_hi20:01
deshantm\o20:01
annegentle#startmeeting20:02
openstackMeeting started Mon Jul 11 20:02:03 2011 UTC.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:02
annegentle#topic action items from last meeting20:02
*** openstack changes topic to "action items from last meeting"20:02
annegentle1. toddmorey and annegentle to work with ttx on making openstack-website project20:02
annegentletoddmorey completed this, making the openstack-org project on Github which he'll cover momentarily20:03
* heckj lurks, but has another meeting conflicting20:03
annegentle2.    annegentle to ask ttx about RSS and subscribing to doc bug feeds - I talked to ttx and found that all doc bugs are tagged and aggregated with openstack bugs at https://bugs.launchpad.net/openstack20:04
annegentleheckj: s'okay :)20:04
annegentleSo that's it on action items. We can move to toddmorey now, on openstack-org20:04
annegentle#topic General documentation status - openstack.org project - now in GitHub20:04
*** openstack changes topic to "General documentation status - openstack.org project - now in GitHub"20:04
annegentletoddmorey, floor's yours20:05
toddmoreyGreat. So as Anne said, the repository (in an early first stage) is now online: https://github.com/toddmorey/openstack-org20:05
toddmoreySo there are two types of involvement with openstack.org: 1. content authoring and 2. design / development20:06
toddmoreythis, of course, is concerning #220:06
toddmoreySeveral folks (anne and stephen, for example) are already working with me on content authorship20:07
annegentle#info Openstack.org design and dev now a GitHub repo20:07
annegentle#link https://github.com/toddmorey/openstack-org20:07
toddmoreythis is a step to include other people who would like to get involved in development of site features, etc.20:07
toddmoreythanks, moderator anne :020:08
annegentletoddmorey: sorry for the unintended interruption, I'm new at this moderator thing :)20:08
annegentletoddmorey: does the repo include bug tracking? I'm also new to Github.20:08
toddmoreythe next step for me is a package of sorts so its super easy to stage the site on a local computer. At any rate, if you'd like to get involved, please don't hesitate to reach out to me: todd@openstack.org20:08
annegentlenot that there are any bugs!20:09
toddmoreyYup! There is issue tracking in github (which we can use) or we could do launchpad if that helps unite with other pieces of the project20:09
toddmoreythough I guess it's all going github over time :)20:09
annegentleyou're a trendsetter I'm sure :)20:10
annegentleany questions?20:10
toddmoreyCreating a new issue for the site is easy: https://github.com/toddmorey/openstack-org/issues20:10
deshantmis there a staging.openstack.org?20:11
deshantmxen.org has one and that makes it easy for us to stage changes before making them live20:11
toddmoreygood question! There is indeed. That URL is live, though it requires an account to see the content20:11
deshantmwe also run out of a git tree and there is just a staging and live branch20:11
toddmorey(mostly to keep robots from crawling it)20:11
annegentletoddmorey: ah, that might be easier than packaging up for local testing?20:12
annegentlepesky robots.20:12
deshantm(ok so i won't tell you what our staging link is ;)20:12
toddmorey#action get folks who would like accounts and create them20:12
mtaylortoddmorey: hey! no plans to move issue tracking to github20:12
toddmoreyuh, maybe I should have made that action make more sense. Is rewording my action another action?20:12
annegentletoddmorey: uh, I dunno?20:13
spectorclan_toddmorey:  is there a review process for postings or does everyone have free for all?20:13
annegentlemtaylor: ok, I wonder if we could log bugs against the openstack-manuals Launchpad project for the openstack.org site?20:13
toddmoreyThere is a review process for sure, but the logistics of it are currently in works.20:13
mtaylorannegentle: potentially? hrm ... should probably think about that20:14
toddmoreySure, guys. Would rather use the standard than create a new one.20:14
annegentlemtaylor: I really like that doc bugs are rolled up under /openstack esp. when tagged correctly. Seems like we can make it work.20:14
mtaylortoddmorey: we're working on review automation (similar to tarmac is now) for the git projects ... would it be helpful to have website hooked in to that?20:14
mtayloras in - we could have things go through review, then get merged, then have jenkins deploy new version of website?20:15
deshantmtoddmore: I think the action item that intended is to publicize the ability to get an account to the community20:15
toddmoreyyes, I think that would be helpful. Let's figure out how to hook it in20:15
toddmoreydeshantm: right you are20:15
mtaylorsweet. I'll add it to the todo list of things we should look at once the actual automation stuff is in place20:15
spectorclan_toddmorey: I can handle the community account process20:15
annegentlemtaylor: yes I also think that'll work well20:15
mtaylorannegentle: and yes - I agree re: bug rollups into the /openstack project20:15
annegentleOk, what actions are there?20:16
jeblairI'm working with monty on the review automation20:16
jeblairnow might be a good time to introduce myself :)20:16
annegentle#action spectorclan_ to handle community account process, email stephen.spector at openstack dot org to request an account20:16
annegentle#action toddmorey and mtaylor to look at hooking up Jenkins for a staging area for openstack.org20:17
annegentlejeblair: sure, introduce yourself, sounds apropos20:17
jeblairMy name is James Blair; I recently joined Rackspace working on the team with Monty, Jay, etc.20:18
annegentlewe love doc automation and staging, welcome aboard!20:18
jeblairI'm starting by helping out monty with the review automation20:18
jeblairthanks!20:18
annegentleok, sounds like we're moving along the "opening openstack.org" path20:19
mtaylorspectorclan_: 'community account process' ... can I butt in and ask what those are accounts to?20:19
spectorclan_mtaylor: people who can edit the OpenStack.org website, not sure we want this but I can have a process built just in case.20:19
annegentlemtaylor: I think the idea would be to provide access to the staging area but keep robots out20:20
mtaylorgreat20:20
toddmoreythose would be CMS author / preview accounts for the staging site20:20
annegentleah, sorry, I'm confusing the two projects - we are talking about 2) design/dev20:20
mtaylorso - definitley loop jeblair and I in on that - again the stuff we're doing for the other projects I think can probably apply to the mechanics of that20:20
mtaylorAH20:20
mtaylorcms author20:20
mtaylorgotcha - I totally follow the words you are saying now20:20
annegentlemtaylor: hee, saying/typing, you know, it's words.20:21
mtaylorbah. words.20:21
annegentleok, thanks for clarifying all. Let's move on...20:21
annegentle#topic RST developer docs updates20:21
*** openstack changes topic to "RST developer docs updates"20:21
annegentleIn no particular order, starting with swift.20:22
annegentleFor swift, we now have archived sites for the 1.4.0 and 1.4.1 release at http://swift.openstack.org/1.4.0 and http://swift.openstack.org/1.4.1.20:22
annegentleTo make those archived sites, you can run a build on the Jenkins server at http://jenkins.openstack.org/view/Swift/job/swift-docs-archive/ and enter the version number and the Launchpad branch that you want to use to build the archived site.20:22
annegentlethank you mtaylor for making the automagic happen20:22
mtayloryay!20:22
mtaylor(although I believe I still have a bug to fix in there somewhere...)20:22
annegentle#link http://jenkins.openstack.org/view/Swift/job/swift-docs-archive/ <- Job that creates archived RST doc site from version number and lp branch20:23
annegentleThat's all the news I know for Swift dev docs.20:23
annegentleThe most recent addition to Nova docs is the Developer reference for the Distributed Scheduler, contributed by Sandy Walsh.20:23
annegentle#link http://nova.openstack.org/devref/distributed_scheduler.html20:23
annegentleexcellent use of "dating service" as a metaphor, thank you sandywalsh!20:24
annegentle#action annegentle to add the distributed scheduler page to the devref index page itself20:24
annegentleThat's all I know for nova dev docs.20:24
annegentleAnd for Glance dev docs, I did get changes to the docs for Glance flags, where glance_api_servers replaces glance_host/glance_port in the compute admin guide20:26
annegentleThanks to Brian Waldon for that update.20:26
annegentleAlso, I wanted to let everyone know that the Rackspace doc tools team provided an RST to Docbook conversion tool in their last sprint.20:27
annegentleSo I can bring over dev docs and write them for ops/devops in DocBook rather handily.20:27
annegentle#topic DocBook docs updates20:28
*** openstack changes topic to "DocBook docs updates"20:28
annegentleDocs on http://docs.openstack.org can have either Apache licensing (if they came from RST docs, for example) or CC licensing (if it came from a blog, for example).20:28
annegentleHopefully this opens up possibilities to more contributors.20:29
toddmoreyawesome!20:29
spectorclan_very cool20:29
annegentleI also spoke with Jacek Artymiak a few weeks back about licensing and collaboration - he recently wrote an ebook about managing Rackspace cloud servers with the openstack-compute tool, and is very interested in working with us.20:30
annegentle#link http://www.readwriteweb.com/cloud/2011/06/how-to-manage-rackspace-cloud.php <- review of his book20:30
annegentleAlways open to more contributors, y'all. :)20:30
annegentle#topic Doc incubation20:30
*** openstack changes topic to "Doc incubation"20:30
annegentleI brought the Keystone dev guide into openstack-manuals last week, and it builds automatically to http://docs.openstack.org/incubation/identitydevguide/content/index.html.20:31
heckjannegentle: re contribution - you're welcome to the FlatNetworking pieces I put on the wiki - tried to make it available for the most folks there.20:31
annegentlethanks again to mtaylor and dwcramer for the help on that one.20:31
annegentleheckj: excellent, thanks.20:31
deshantmwhat is doc incubation?20:32
annegentleheckj: I took a look at bringing wiki markup into docbook and the HTML that MoinMoin outputs is miserable, but I'll look again soon.20:32
annegentledeshantm: Doc incubation is the process for brining relevant documentation under the docs.openstack.org umbrella once the Project Policy Board votes to incubate a project.20:32
deshantmah ok thanks20:33
heckjannegentle: I'm happy to help translate if needed, but I don't know docbook, and my initial forays into trying to edit it were tinged with horror20:33
annegentlein this case, Keystone had a DocBook Dev Guide ready to release, so under the umbrella it went.20:33
annegentleheckj: horror! :)20:33
dwcramerheckj: MoinMoin can output to DocBook. That might be worth exploring.20:33
annegentleheckj: we can work on a path20:33
annegentledwcramer: nice20:33
annegentle#action explore MoinMoin to DocBook paths20:33
*** adjohn has joined #openstack-meeting20:33
annegentleOne other note on incubation, there's also the Extensions Guide that is under pre-incubation now20:34
annegentleThe docs don't necessarily distinguish between "already incubated" and "applying for incubation"20:35
annegentleOk, guess I'll open it up for open discussion20:35
annegentle#topic Open discussion20:35
*** openstack changes topic to "Open discussion"20:35
annegentleI do have one item that seems low-hanging fruit to me. If anyone is interested in uploading man pages for Debian, there are stub files available. I think it's a copy/paste job.20:36
deshantmtoddmorey: did you get my email about the idea of having a redirect from blog.openstack.org to openstack.org/blog20:36
annegentleFor example, see http://cdn.debian.net/debian/pool/main/s/swift/ . You'd replace the stub files in the debian/mans folder of20:36
annegentlethe .debian.tar.gz file.20:36
heckjA number of doc updates will be needed around installing OpenStack and the nova-manage commands (some of which have changed recently)20:36
toddmoreyI did! I asked for that to be set up. Very sensible request.20:37
annegentleheckj: yes, also the nova-manage network create command now requires public or private.20:37
toddmoreyI do the same thing. :)20:37
annegentleI've started updating in trunk - such as http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-networking-on-the-compute-node.html20:37
heckjannegentle: Great! Wanted to make sure that wasn't missed.20:38
annegentleheckj: would love help with the editing passes, maybe we'll get you ramped up on DocBook :)20:38
deshantmI was talking to a user the other day that had some confusion about which version of the nova/euca tools work with which version of openstack20:38
heckjI think we also need to be even handed with handing out links to install mechanisms - both Puppet, Chef, and the various scripts and distributions. The wiki implies some over others right now.20:39
deshantmis there a place that documents the various interactions?20:39
annegentledeshantm: that's a good question. I know soren started http://wiki.openstack.org/Nova/EucalyptusFeatureComparison20:39
heckjannegentle: Would be happy to help read through & edit! Just need to get over the hump with DocBook20:39
heckjdeshantm: It's a bit of an ongoing discussion when it comes down to APIs too - the euca-upload-images, for example, doesn't work with the Glance pieces to my knowledge, and many examples are starting to switch from using Euca commands to OpenStack API commands.20:40
deshantmok so is there a good place to track this discussion and outcomes of it in order have a nice place to point users?20:41
annegentledeshantm: I think some of the difficulty also lies in using the API spec as a Dev Guide.20:41
heckjdeshantm: I don't think there's one place - it's all over20:41
annegentledeshantm: it's a reuse that means it's hard to know where that info should live20:41
annegentleright, the scattering is what I'm getting at too. Where should such info live?20:42
annegentleon the wiki for starters?20:42
deshantmok I'm fine following the situation and synthesizing for users if I know what to follow20:42
spectorclan_Great meeting anne, have to run. Thanks,20:43
spectorclan_exit20:43
*** spectorclan_ has quit IRC20:43
annegentledeshantm: for example, the API 1.1 spec just updated20:43
heckjReasonable - easy to edit and accessible to anyone. We might want to mark some specific wiki pages to indicate they're sourcing information - there's enough happening in that wiki it's getting a little hard to distinguish signal from noise.20:43
deshantmI'm planning on doing some OpenStack testing for work20:43
annegentlebut that Dev Guide doesn't provide "use this and this and it'll work"20:43
annegentleheckj: agree on the signal/noise difficulty on the wiki. Do we just need a new section written in the Compute Admin Guide?20:44
annegentleor, is it a brutally honest wiki page that best serves this purpose (clarifying which version of the nova/euca tools work with which version of member:openstack)20:44
* annegentle leans towards brutally honest wiki page for now20:45
deshantmit seems like this is more of a wiki thing until things stablize20:45
annegentlesounds good.20:45
* heckj agrees with brutal honest wiki page20:45
annegentle#action annegentle to start wiki page to clarify which version of the nova/euca tools work with which version of openstack distro20:46
heckjWe need to keep it super easy to edit, and maybe just closely monitored/edited20:46
annegentledeshantm: like what you're doing towards Xen packaging, thanks for doing that, it'll help immensely with docs20:46
deshantmannegentle: can you email that wiki page out once it is created so I can folow it and try to help20:46
heckjI'm reacting a bit to StackOps page on the wiki which encourages folks to use their Distro, but has a number of holes they don't appear to be responding to.20:46
deshantmannegentle: Yeah, I also found a docs bug about the xenapi plugins20:47
annegentleheckj: we can all do our part to spackle :)20:47
deshantmonce this gets resolved I'll update that bug20:47
annegentleok, thanks. Any thing else from any one else?20:47
deshantmI'll also need to go back and add the relevant information the compute admin guide20:47
annegentledeshantm: great, that would be excellent20:48
deshantmthat's all I can think of for now20:48
deshantmthanks20:48
annegentleok, thanks all20:48
annegentle#endmeeting20:48
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:48
openstackMeeting ended Mon Jul 11 20:48:23 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-11-20.02.html20:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-11-20.02.txt20:48
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-11-20.02.log.html20:48
*** msinhore has quit IRC20:59
*** msinhore has joined #openstack-meeting21:15
*** mattray has quit IRC21:15
*** mattray has joined #openstack-meeting21:22
*** msinhore has quit IRC21:44
*** msinhore has joined #openstack-meeting22:16
*** dwcramer has quit IRC22:21
*** mattray has quit IRC22:40
*** edconzel_ has joined #openstack-meeting22:46
*** edconzel has quit IRC22:48
*** msinhore has quit IRC22:48
*** msinhore has joined #openstack-meeting22:48
*** edconzel_ has quit IRC22:51
*** adjohn has quit IRC22:59
*** msinhore1 has joined #openstack-meeting22:59
*** msinhore has quit IRC23:00
*** msinhore has joined #openstack-meeting23:01
*** troytoman is now known as troytoman-away23:02
*** msinhore1 has quit IRC23:03
*** rnirmal has quit IRC23:03
*** jkoelker has quit IRC23:04
*** joearnold has quit IRC23:14
*** msinhore has quit IRC23:17
*** msinhore has joined #openstack-meeting23:17
*** vladimir3p has quit IRC23:22
*** mencken has left #openstack-meeting23:31
*** msinhore has quit IRC23:38
*** msinhore has joined #openstack-meeting23:38
*** msinhore has quit IRC23:43
*** msinhore has joined #openstack-meeting23:43

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