From berendt at b1-systems.de  Mon Sep  1 10:42:26 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Mon, 01 Sep 2014 12:42:26 +0200
Subject: [Openstack-docs] Adding redirects to .htaccess for renamed files
In-Reply-To: <CABA+jQodDM4BKC1aT=wSMubZWJq8kc1GWmecQpjs9aJH54HU1Q@mail.gmail.com>
References: <CABA+jQodDM4BKC1aT=wSMubZWJq8kc1GWmecQpjs9aJH54HU1Q@mail.gmail.com>
Message-ID: <54044D92.7030002@b1-systems.de>

On 08/29/2014 04:15 PM, Matt Kassawara wrote:
> Apparently we need to add redirects to .htaccess after renaming files.
> Since the installation guide produces four different HTML versions, each
> file renamed requires four entries in .htaccess which doesn't scale. How
> can we improve it?

Using redirectmatch instead of redirect should work.

Something like this (not tested):

redirectmatch 301
/trunk/install-guide/install/(apt|apt-debian|zypper|yum)/content/ch_basics.html
/trunk/install-guide/install/$1/content/ch_basic_environment.html

Christian.

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From aj at suse.com  Mon Sep  1 13:45:05 2014
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 01 Sep 2014 15:45:05 +0200
Subject: [Openstack-docs] Redirects for /trunk/install-guide?
Message-ID: <54047861.8020404@suse.com>

I suggest to not do any redirects for /trunk/install-guide - this is the
draft version and we should not do redirects for any change there.

https://review.openstack.org/#/c/118130

Does this work for you?

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From berendt at b1-systems.de  Mon Sep  1 14:55:11 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Mon, 01 Sep 2014 16:55:11 +0200
Subject: [Openstack-docs] Redirects for /trunk/install-guide?
In-Reply-To: <54047861.8020404@suse.com>
References: <54047861.8020404@suse.com>
Message-ID: <540488CF.70809@b1-systems.de>

On 09/01/2014 03:45 PM, Andreas Jaeger wrote:
> I suggest to not do any redirects for /trunk/install-guide - this is the
> draft version and we should not do redirects for any change there.
> 
> https://review.openstack.org/#/c/118130
> 
> Does this work for you?

Yes. I think it is better to remove them instead of rewriting them. The
review requests was a demonstration for "Adding redirects to .htaccess
for renamed files". I'll update the referenced review request.

Christian.

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From maishsk+openstack at maishsk.com  Tue Sep  2 14:41:14 2014
From: maishsk+openstack at maishsk.com (Maish Saidel-Keesing)
Date: Tue, 02 Sep 2014 17:41:14 +0300
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
	team
In-Reply-To: <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
Message-ID: <5405D70A.1040905@maishsk.com>

As would I...


On 26/08/2014 21:48, Adam Lawson wrote:
>
> I'd be happy to participate as needed Anne.
>
> On Aug 26, 2014 11:10 AM, "Anne Gentle" <anne at openstack.org
> <mailto:anne at openstack.org>> wrote:
>
>     Hi all, 
>     Cross-posting to -docs and -operators. 
>
>     At the Ops mid-cycle meetup this week, Matt Griffin, David
>     Medberry, and Sriram Subramanian offered to start a review team
>     for the High Availability Guide. It needs some updates and it's
>     best if the review team works similar to the Security Guide --
>     subject matter experts working with core docs team members for
>     reviews. So I'm proposing we pull it into its own repo just like
>     the Security Guide. Any reasons not to? I think the next steps are:
>
>     1. Propose a patch to openstack/governance to show the repo is
>     governed by the Docs program.
>     2. Propose a patch that sets up a separate review team starting
>     with Matt, David, and Sriram. We think Emilien would be interested
>     too, sound good? Any others? We can have members of
>     openstack-docs-core as well, similar to the Security Guide.
>     3. Propose a patch that gets that guide building separately in a
>     different repo.
>     4.  Start working on the four bugs already logged [1] and logged
>     more as needed.
>
>     Any other subtasks? Any interested parties? 
>
>     Thanks,
>     Anne
>
>     1. https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide
>
>     _______________________________________________
>     OpenStack-operators mailing list
>     OpenStack-operators at lists.openstack.org
>     <mailto:OpenStack-operators at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-- 
Maish Saidel-Keesing

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140902/e9ad4563/attachment.html>

From Greg.Waines at windriver.com  Wed Sep  3 00:05:10 2014
From: Greg.Waines at windriver.com (Waines, Greg)
Date: Wed, 3 Sep 2014 00:05:10 +0000
Subject: [Openstack-docs] 2013.2 tag seems broken ?
Message-ID: <5058BED8BBDF5D4F898AD4366E6B36E02433DDA2@ALA-MBB.corp.ad.wrs.com>

A question about the 2013.2 tag on the openstack doc APIs ...

Background:

?         my company, WindRiver, provides an enhanced OpenStack distribution

?         which has resulted in us extending/enhancing the OpenStack REST APIs

?

?         In order to provide updated OpenStack REST APIs, we are:

o   including the api-site, compute-api, image-api, etc.  gits
as sub-gits in our git repository

o   and

o   the plan is for us to increment our changes on top of these opensource gits

Question:

?         the latest git 'tag' for these api doc gits seems to be '2013.2'

?         so we have included the sub-gits at this tag

?

?         however

o   when I try to generate sources

o   i.e.    mvn clean generate-sources

o   in (say) the compute-api git, I have the following problems:

?  in ./compute-api/openstack-compute-api-2/src/

?         in file:  os-compute-devguide.xml:
...
            <wadl:resources
                xmlns:wadl="http://wadl.dev.java.net/2009/02">
                <wadl:resource
                    href="http://git.openstack.org/cgit/openstack/api-site/plain/api-ref/src/wadls/compute-api/src/wadl/os-compute-2.wadl#ips"/>
                <wadl:resource
                    href="http://git.openstack.org/cgit/openstack/api-site/plain/api-ref/src/wadls/compute-api/src/wadl/os-compute-2.wadl#network_label"
                />
            </wadl:resources>
...

?         ??? this 'plain' directory does not exist in the 'api-site' git ???

o   ... so the make of the PDF fails.

o

o   ... and for me (and maybe others doing the same doc extensions as me),
it is not good to be referencing the .wadl files from the api-site git @ //git.openstack.org ...
instead of a local version of this api-site git.

o

?

?         I do notice that in the current/master version of the api-site and compute-api gits,
almost everything seems to be moved to the api-site git ... i.e. there is an api-ref-guides/ directory now in api-site

o   ??? maybe this was to deal with the cross-git reference issues ???

o

?

?         finally, ... how come there are no more recent tags than '2013.2' ?

o   ideally would be nice if there was a tag that represented the version of openstack that the documentation was consistent with e.g. 'havana' or 'icehouse' ...


thanks in advance,
Greg.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140903/5e98357b/attachment-0001.html>

From anne at openstack.org  Wed Sep  3 03:36:27 2014
From: anne at openstack.org (Anne Gentle)
Date: Tue, 2 Sep 2014 22:36:27 -0500
Subject: [Openstack-docs] 2013.2 tag seems broken ?
In-Reply-To: <5058BED8BBDF5D4F898AD4366E6B36E02433DDA2@ALA-MBB.corp.ad.wrs.com>
References: <5058BED8BBDF5D4F898AD4366E6B36E02433DDA2@ALA-MBB.corp.ad.wrs.com>
Message-ID: <CAD0KtVG797Sa06reg+CmkpxLwTpfYpikh85C8oJ_xNE7VFtbBA@mail.gmail.com>

On Tue, Sep 2, 2014 at 7:05 PM, Waines, Greg <Greg.Waines at windriver.com>
wrote:

>  A question about the 2013.2 tag on the openstack doc APIs ?
>
>
>
> Background:
>
> ?         my company, WindRiver, provides an enhanced OpenStack
> distribution
>
> ?         which has resulted in us extending/enhancing the OpenStack REST
> APIs
>
> ?
>
> ?         In order to provide updated OpenStack REST APIs, we are:
>
> o   including the api-site, compute-api, image-api, etc.  gits
> as sub-gits in our git repository
>
> o   and
>
> o   the plan is for us to increment our changes on top of these
> opensource gits
>
>
>
> Question:
>
> ?         the latest git ?tag? for these api doc gits seems to be ?2013.2?
>
> We originally tagged this repo just for tracking stats if my memory
serves. There's no meaning to a "release" of API docs, because we (upstream
docs for OpenStack) cannot predict how a cloud provider will implement
their API endpoints and which API versions they will implement.


> ?         so we have included the sub-gits at this tag
>
> ?
>
> ?         however
>
> o   when I try to generate sources
>
> o   i.e.    mvn clean generate-sources
>
> o   in (say) the compute-api git, I have the following problems:
>
> ?  in ./compute-api/openstack-compute-api-2/src/
>
> ?         in file:  os-compute-devguide.xml:
>
> ?
>
>             <wadl:resources
>
>                 xmlns:wadl="http://wadl.dev.java.net/2009/02">
>
>                 <wadl:resource
>
>                     href="
> http://git.openstack.org/cgit/openstack/api-site/plain/api-ref/src/wadls/compute-api/src/wadl/os-compute-2.wadl#ips
> "/>
>
>                 <wadl:resource
>
>                     href="
> http://git.openstack.org/cgit/openstack/api-site/plain/api-ref/src/wadls/compute-api/src/wadl/os-compute-2.wadl#network_label
> "
>
>                 />
>
>             </wadl:resources>
>
> ?
>
> ?         ??? this ?plain? directory does not exist in the ?api-site? git
> ???
>
> o   ? so the make of the PDF fails.
>
>
Right, it's "raw" in github and "plain" in our mirror.


> o
>
> o   ? and for me (and maybe others doing the same doc extensions as me),
> it is not good to be referencing the .wadl files from the api-site git @ //
> git.openstack.org ?
> instead of a local version of this api-site git.
>
> o
>
> ?
>
> ?         I do notice that in the current/master version of the api-site
> and compute-api gits,
> almost everything seems to be moved to the api-site git ? i.e. there is an
> api-ref-guides/ directory now in api-site
>
> o   ??? maybe this was to deal with the cross-git reference issues ???
>
> o
>

There are two reasons going on here:
1. We, upstream OpenStack, can't rely on github to be there with the uptime
we need, so we mirror it with our own infra resources.
2. Yes, we had problems building when we had to rely on a change in two
separate repos to land with similar timing.


>  ?
>
> ?         finally, ? how come there are no more recent tags than ?2013.2?
> ?
>
> o   ideally would be nice if there was a tag that represented the version
> of openstack that the documentation was consistent with e.g. ?havana? or
> ?icehouse? ?
>
>
We have had this discussion in the past, read it at
http://lists.openstack.org/pipermail/openstack-docs/2014-April/004337.html.
The basic problem with tagging API docs is that there's not a map from say,
havana, to API versions. The deployers choices for that particular release
would look something like this:

Block Storage API v1 or v2
Compute API v2
Identity API v2.0 or v3
Image Service v1, v1.1, or v2
(not Database service, they weren't integrated then)
Networking API v2.0
Object Storage v1
Orchestration v1
Telemetry v2

So I think there are  3*2*3*4*2*2*2*2 = 1152 possibilities of combining API
versions a cloud provider offers for Havana, where you can choose not to
deploy an API endpoint at all. We can't dictate to the provider "you must
run these API versions when running havana" so I've avoided tagging the
docs for overhead and maintenance and explanatory reasons. :)

Hopefully these explanations makes sense to you, sounds like you've guessed
right all along. I certainly want our docs to be re-used and they're
licensed completely for re-use, but I'm pretty sure I can't accurately say
which API calls go with a particular release. I definitely want to hear
ideas though!
Thanks for asking -
Anne



>
>
>
>
> thanks in advance,
>
> Greg.
>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140902/d6781f84/attachment-0001.html>

From berendt at b1-systems.de  Wed Sep  3 07:23:35 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Wed, 03 Sep 2014 09:23:35 +0200
Subject: [Openstack-docs] Please re-review 113076
Message-ID: <5406C1F7.8050905@b1-systems.de>

Something is wrong with review request 113076
(https://review.openstack.org/#/c/113076/). Changed it to -2. I do not
know how to change/stop the workflow.

1. Matthew approved the change without any other +2.
2. There is an similiary change implementing parts of this change
(https://review.openstack.org/#/c/117327/).

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From aj at suse.com  Wed Sep  3 08:00:40 2014
From: aj at suse.com (Andreas Jaeger)
Date: Wed, 03 Sep 2014 10:00:40 +0200
Subject: [Openstack-docs] Please re-review 113076
In-Reply-To: <5406C1F7.8050905@b1-systems.de>
References: <5406C1F7.8050905@b1-systems.de>
Message-ID: <5406CAA8.4080600@suse.com>

On 09/03/2014 09:23 AM, Christian Berendt wrote:
> Something is wrong with review request 113076
> (https://review.openstack.org/#/c/113076/). Changed it to -2. I do not
> know how to change/stop the workflow.
> 
> 1. Matthew approved the change without any other +2.

He approved while there was still a WIP set.

The next person doing an approval will get this in ;) - but only if
there's no -2.


> 2. There is an similiary change implementing parts of this change
> (https://review.openstack.org/#/c/117327/).

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From Greg.Waines at windriver.com  Wed Sep  3 15:20:36 2014
From: Greg.Waines at windriver.com (Waines, Greg)
Date: Wed, 3 Sep 2014 15:20:36 +0000
Subject: [Openstack-docs] 2013.2 tag seems broken ?
In-Reply-To: <CAD0KtVG797Sa06reg+CmkpxLwTpfYpikh85C8oJ_xNE7VFtbBA@mail.gmail.com>
References: <5058BED8BBDF5D4F898AD4366E6B36E02433DDA2@ALA-MBB.corp.ad.wrs.com>
 <CAD0KtVG797Sa06reg+CmkpxLwTpfYpikh85C8oJ_xNE7VFtbBA@mail.gmail.com>
Message-ID: <5058BED8BBDF5D4F898AD4366E6B36E02433E2AE@ALA-MBB.corp.ad.wrs.com>

Thanks Anne.

But the individual APIs, say Compute API, are not up-versioned every OpenStack Release.

However the individual APIs, say Compute API V2, (I believe) are extended every OpenStack Release ? possibly new requests, possibly new parameters for requests, possibly new attributes in responses.

So there are going to be IceHouse(say)-specific changes in (say) Compute API V2 ? correct ?

But it sounds like there is no tag or commit that represents an ?up-to-Havana only? version of Compute API V2 ? correct ?


Greg.





From: annegentle at justwriteclick.com [mailto:annegentle at justwriteclick.com] On Behalf Of Anne Gentle
Sent: Tuesday, September 02, 2014 11:36 PM
To: Waines, Greg
Cc: openstack-docs at lists.openstack.org
Subject: Re: [Openstack-docs] 2013.2 tag seems broken ?



< SNIP >



We have had this discussion in the past, read it at http://lists.openstack.org/pipermail/openstack-docs/2014-April/004337.html. The basic problem with tagging API docs is that there's not a map from say, havana, to API versions. The deployers choices for that particular release would look something like this:

Block Storage API v1 or v2
Compute API v2
Identity API v2.0 or v3
Image Service v1, v1.1, or v2
(not Database service, they weren't integrated then)
Networking API v2.0
Object Storage v1
Orchestration v1
Telemetry v2

So I think there are  3*2*3*4*2*2*2*2 = 1152 possibilities of combining API versions a cloud provider offers for Havana, where you can choose not to deploy an API endpoint at all. We can't dictate to the provider "you must run these API versions when running havana" so I've avoided tagging the docs for overhead and maintenance and explanatory reasons. :)

Hopefully these explanations makes sense to you, sounds like you've guessed right all along. I certainly want our docs to be re-used and they're licensed completely for re-use, but I'm pretty sure I can't accurately say which API calls go with a particular release. I definitely want to hear ideas though!
Thanks for asking -
Anne




thanks in advance,
Greg.


_______________________________________________
Openstack-docs mailing list
Openstack-docs at lists.openstack.org<mailto:Openstack-docs at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140903/dea2681e/attachment.html>

From nchase at mirantis.com  Wed Sep  3 15:38:25 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Wed, 03 Sep 2014 11:38:25 -0400
Subject: [Openstack-docs] Please re-review 113076
In-Reply-To: <5406CAA8.4080600@suse.com>
References: <5406C1F7.8050905@b1-systems.de> <5406CAA8.4080600@suse.com>
Message-ID: <540735F1.6040502@mirantis.com>

This was part of an attempt to get the Networking Guide changes all in 
one document so we can evaluate what we have and where we need to go.   
We have realized that's not practical at this point. :(

----  Nick

On 9/3/2014 4:00 AM, Andreas Jaeger wrote:
> On 09/03/2014 09:23 AM, Christian Berendt wrote:
>> Something is wrong with review request 113076
>> (https://review.openstack.org/#/c/113076/). Changed it to -2. I do not
>> know how to change/stop the workflow.
>>
>> 1. Matthew approved the change without any other +2.
> He approved while there was still a WIP set.
>
> The next person doing an approval will get this in ;) - but only if
> there's no -2.
>
>
>> 2. There is an similiary change implementing parts of this change
>> (https://review.openstack.org/#/c/117327/).
> Andreas

-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
<http://openstacksv.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140903/674e96e1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140903/674e96e1/attachment-0001.png>

From mkassawara at gmail.com  Wed Sep  3 18:45:11 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Wed, 3 Sep 2014 13:45:11 -0500
Subject: [Openstack-docs] Discussion for bug #1340524
Message-ID: <CABA+jQojZ-6YSrDxLjMxmcMBi7HmZLbKZY9D7SF=dpHbX+n11w@mail.gmail.com>

I'm looking at bug #1340524 [1] and trying to determine the best course of
action.

Similar to other chapters, the Networking chapter contains an
introduction/concepts section. However, it references content local to the
installation guide rather than content in the common directory. I could
merge the local and common content, but the common content would contain
much more information than other services and somewhat reference the
specific configuration in the installation guide. The common content also
doesn't cover nova-network if we decide to retain it for Juno.

Looking for ideas!

[1] https://bugs.launchpad.net/openstack-manuals/+bug/1340524
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140903/323e92d0/attachment.html>

From berendt at b1-systems.de  Thu Sep  4 08:45:59 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Thu, 04 Sep 2014 10:45:59 +0200
Subject: [Openstack-docs] Please re-review 113076
In-Reply-To: <540735F1.6040502@mirantis.com>
References: <5406C1F7.8050905@b1-systems.de> <5406CAA8.4080600@suse.com>
 <540735F1.6040502@mirantis.com>
Message-ID: <540826C7.4040003@b1-systems.de>

On 09/03/2014 05:38 PM, Nicholas Chase wrote:
> This was part of an attempt to get the Networking Guide changes all in
> one document so we can evaluate what we have and where we need to go.  
> We have realized that's not practical at this point. :(

Can we abandon the review request?

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From tom at openstack.org  Thu Sep  4 10:29:14 2014
From: tom at openstack.org (Tom Fifield)
Date: Thu, 04 Sep 2014 18:29:14 +0800
Subject: [Openstack-docs] Proposal: Bug Squashing day on the 9th of
	September
In-Reply-To: <00f228af4c0d116d8e2cb92daba0fa87@objectif-libre.com>
References: <53E3D0F6.7040903@suse.com>
 <CAD0KtVEsCgzbQvbscdS-XsheVsRbQfKe2BtGwxYXL3jWDtxxrA@mail.gmail.com>
 <53EA6CB7.7070503@suse.com>
 <00f228af4c0d116d8e2cb92daba0fa87@objectif-libre.com>
Message-ID: <54083EFA.7000703@openstack.org>

On 18/08/14 23:18, Gauvain Pocentek wrote:
> Le 2014-08-12 21:36, Andreas Jaeger a ?crit :
>> On 08/12/2014 05:29 PM, Anne Gentle wrote:
>>> Thanks Andreas! Sounds like we have a good day and start. I'll add it to
>>> this week's What's Up Doc and we'll plan for 9/9/14 bug squashing.
>>
>> I noticed that many bugs can be fixed with the autogeneration of our
>> tables.
>>
>> Gauvain, could you do a run before the 9th, please? That way we might be
>> able to close many bugs as fixed since the values are already in...
> 
> Sure!

Hi,

I've done a fast triage run of the 'new' bugs in openstack-manuals. We
now have 442 confirmed bugs (650+ if you count api-site too) ready for
the bug day.

Found a couple of good low-hanging-fruit s, which have been tagged
appropriately for newcomers.

Regards,


Tom



From nchase at mirantis.com  Thu Sep  4 15:00:19 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Thu, 04 Sep 2014 11:00:19 -0400
Subject: [Openstack-docs] Please re-review 113076
In-Reply-To: <540826C7.4040003@b1-systems.de>
References: <5406C1F7.8050905@b1-systems.de> <5406CAA8.4080600@suse.com>
 <540735F1.6040502@mirantis.com> <540826C7.4040003@b1-systems.de>
Message-ID: <54087E83.4070202@mirantis.com>


Yes, I think so; we are re-working how we're getting this done anyway.

Thanks!

----  Nick

On 9/4/2014 4:45 AM, Christian Berendt wrote:
> On 09/03/2014 05:38 PM, Nicholas Chase wrote:
>> This was part of an attempt to get the Networking Guide changes all in
>> one document so we can evaluate what we have and where we need to go.
>> We have realized that's not practical at this point. :(
> Can we abandon the review request?
>

-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
<http://openstacksv.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140904/3591a562/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140904/3591a562/attachment.png>

From anne at openstack.org  Thu Sep  4 19:37:00 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 4 Sep 2014 14:37:00 -0500
Subject: [Openstack-docs] Discussion for bug #1340524
In-Reply-To: <CABA+jQojZ-6YSrDxLjMxmcMBi7HmZLbKZY9D7SF=dpHbX+n11w@mail.gmail.com>
References: <CABA+jQojZ-6YSrDxLjMxmcMBi7HmZLbKZY9D7SF=dpHbX+n11w@mail.gmail.com>
Message-ID: <CAD0KtVFEqU2udZVU-VD4uxqx6CpSZ_qV-mJF16qT4mfFR9aGrg@mail.gmail.com>

On Wed, Sep 3, 2014 at 1:45 PM, Matt Kassawara <mkassawara at gmail.com> wrote:

> I'm looking at bug #1340524 [1] and trying to determine the best course of
> action.
>
> Similar to other chapters, the Networking chapter contains an
> introduction/concepts section. However, it references content local to the
> installation guide rather than content in the common directory. I could
> merge the local and common content, but the common content would contain
> much more information than other services and somewhat reference the
> specific configuration in the installation guide. The common content also
> doesn't cover nova-network if we decide to retain it for Juno.
>
>
Specific to that bug, Marco is looking for a list of services and daemons.
I think he wrote a list for nova (
https://bugs.launchpad.net/openstack-manuals/+bug/1160757) that looks like
a fairly easy bug to fix as long as we agree on where -- which is what
you're asking here, right?

He would like something similar for CLIs:
https://bugs.launchpad.net/openstack-manuals/+bug/1238668

So ideally we'd provide complete per-project information modularly and
insert it into each book as needed. I think that people like Marco want the
big picture put into logical pieces.

Common content is only common when it's needed in two places. I think the
nova section should cover nova-network, and then add a neutron listing. Is
that helpful?

Anne


> Looking for ideas!
>
> [1] https://bugs.launchpad.net/openstack-manuals/+bug/1340524
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140904/c5349fe9/attachment.html>

From anne at openstack.org  Thu Sep  4 20:49:30 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 4 Sep 2014 15:49:30 -0500
Subject: [Openstack-docs] 2013.2 tag seems broken ?
In-Reply-To: <5058BED8BBDF5D4F898AD4366E6B36E02433E2AE@ALA-MBB.corp.ad.wrs.com>
References: <5058BED8BBDF5D4F898AD4366E6B36E02433DDA2@ALA-MBB.corp.ad.wrs.com>
 <CAD0KtVG797Sa06reg+CmkpxLwTpfYpikh85C8oJ_xNE7VFtbBA@mail.gmail.com>
 <5058BED8BBDF5D4F898AD4366E6B36E02433E2AE@ALA-MBB.corp.ad.wrs.com>
Message-ID: <CAD0KtVEJ-SDenpzenCgkpXKF_0vuK3-B=ZYo1r3MgefaUQC6kw@mail.gmail.com>

On Wed, Sep 3, 2014 at 10:20 AM, Waines, Greg <Greg.Waines at windriver.com>
wrote:

>  Thanks Anne.
>
>
>
> But the individual APIs, say Compute API, are not up-versioned every
> OpenStack Release.
>
>
>
> However the individual APIs, say Compute API V2, (I believe) are extended
> every OpenStack Release ? possibly new requests, possibly new parameters
> for requests, possibly new attributes in responses.
>
>
>

Yes, this is correct, extension only happens in extensions though for v2. I
cannot say v2 itself changes, it does not. Extensions may be added or
removed however. A cloud provider then choses what to put into production
for their customers.


>  So there are going to be IceHouse(say)-specific changes in (say) Compute
> API V2 ? correct ?
>
>
>

Yes. Those are mostly tracked with blueprints if you want to know what
actually changed in a given release, such as:
https://blueprints.launchpad.net/nova/icehouse




>  But it sounds like there is no tag or commit that represents an
> ?up-to-Havana only? version of Compute API V2 ? correct ?
>
>
>

Not for the docs. I've been trying to figure out how you could figure it
out from the code itself but not really finding a way even after reading
lots of specs about microversions.

The API docs also are not complete any given release, sad to say. The
mechanism for adding a new extension should include a "DocImpact" flag in
the commit, which then adds a doc bug automatically. I know we try to
quantify and track -- there are 32 bugs outstanding for Compute API for
example:

https://bugs.launchpad.net/openstack-api-site/+bugs/?field.tag=nova

If you have ideas for how we can improve, I'd be happy to hear them. We
didn't get traction on a "registry" idea back in 2012. We also haven't seen
much compliance on doc requirements on extensions themselves. It's
certainly a worthwhile pursuit, but mostly the cloud providers are
documenting their own clouds. OpenStack upstream should document the
standard more than the release is my current thinking.
Anne


>
>
> Greg.
>
>
>
>
>
>
>
>
>
>
>
> *From:* annegentle at justwriteclick.com [mailto:
> annegentle at justwriteclick.com] *On Behalf Of *Anne Gentle
> *Sent:* Tuesday, September 02, 2014 11:36 PM
> *To:* Waines, Greg
> *Cc:* openstack-docs at lists.openstack.org
> *Subject:* Re: [Openstack-docs] 2013.2 tag seems broken ?
>
>
>
>
>
>  < SNIP >
>
>
>
>
>
> We have had this discussion in the past, read it at
> http://lists.openstack.org/pipermail/openstack-docs/2014-April/004337.html.
> The basic problem with tagging API docs is that there's not a map from say,
> havana, to API versions. The deployers choices for that particular release
> would look something like this:
>
>
>
> Block Storage API v1 or v2
>
> Compute API v2
>
> Identity API v2.0 or v3
>
> Image Service v1, v1.1, or v2
>
> (not Database service, they weren't integrated then)
>
> Networking API v2.0
>
> Object Storage v1
>
> Orchestration v1
>
> Telemetry v2
>
>
>
> So I think there are  3*2*3*4*2*2*2*2 = 1152 possibilities of combining
> API versions a cloud provider offers for Havana, where you can choose not
> to deploy an API endpoint at all. We can't dictate to the provider "you
> must run these API versions when running havana" so I've avoided tagging
> the docs for overhead and maintenance and explanatory reasons. :)
>
>
>
> Hopefully these explanations makes sense to you, sounds like you've
> guessed right all along. I certainly want our docs to be re-used and
> they're licensed completely for re-use, but I'm pretty sure I can't
> accurately say which API calls go with a particular release. I definitely
> want to hear ideas though!
>
> Thanks for asking -
>
> Anne
>
>
>
>
>
>
>
>
>
> thanks in advance,
>
> Greg.
>
>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140904/0c0a4e5f/attachment-0001.html>

From anne at openstack.org  Fri Sep  5 13:38:12 2014
From: anne at openstack.org (Anne Gentle)
Date: Fri, 5 Sep 2014 08:38:12 -0500
Subject: [Openstack-docs] use of "weighter"
Message-ID: <CAD0KtVFY_-6jynp9xBKgYyTUz+yy4A8QDuCkmCM8JreTkOX0vg@mail.gmail.com>

Hi all, Looking at https://review.openstack.org/#/c/113890 and
https://review.openstack.org/#/c/118673/ you can see there's difficulty
documenting an option called scheduler_default_weighters and I'm seeking
help from the cinder team with this message.

As far as I can tell, weighters is not a word. Weigh is the verb, weight is
the noun, and much to my surprise, weighers as a noun is a correct use.

So I'm asking John if it's possible to rename scheduler_default_weighters
to scheduler_default_weighers (or scheduler_default_weights) -- not to
bikeshed but because it's tough to document the way it is now and causing
confusion.

Any thoughts on how difficult that would be? The patches above show the
awkwardness we're trying to smooth out.
Thanks,
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140905/93309a00/attachment.html>

From Greg.Waines at windriver.com  Fri Sep  5 13:59:07 2014
From: Greg.Waines at windriver.com (Waines, Greg)
Date: Fri, 5 Sep 2014 13:59:07 +0000
Subject: [Openstack-docs] Modifying the 'front page' of the REST API Docs ?
Message-ID: <5058BED8BBDF5D4F898AD4366E6B36E02433EE14@ALA-MBB.corp.ad.wrs.com>

Does anyone know how to modify the front page of the PDF file that gets generated when building (mvn clean generate-sources) the rest api documentation ?

i.e. in order to be able to put company-specific branding on the document.


Greg.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140905/aabcd28d/attachment.html>

From aj at suse.com  Fri Sep  5 14:00:00 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 05 Sep 2014 16:00:00 +0200
Subject: [Openstack-docs] use of "weighter"
In-Reply-To: <CAD0KtVFY_-6jynp9xBKgYyTUz+yy4A8QDuCkmCM8JreTkOX0vg@mail.gmail.com>
References: <CAD0KtVFY_-6jynp9xBKgYyTUz+yy4A8QDuCkmCM8JreTkOX0vg@mail.gmail.com>
Message-ID: <5409C1E0.6000200@suse.com>

On 09/05/2014 03:38 PM, Anne Gentle wrote:
> Hi all, Looking at https://review.openstack.org/#/c/113890 and
> https://review.openstack.org/#/c/118673/ you can see there's difficulty
> documenting an option called scheduler_default_weighters and I'm seeking
> help from the cinder team with this message.
> 
> As far as I can tell, weighters is not a word. Weigh is the verb, weight
> is the noun, and much to my surprise, weighers as a noun is a correct use.
> 
> So I'm asking John if it's possible to rename
> scheduler_default_weighters to scheduler_default_weighers (or
> scheduler_default_weights) -- not to bikeshed but because it's tough to
> document the way it is now and causing confusion.
> 
> Any thoughts on how difficult that would be? The patches above show the
> awkwardness we're trying to smooth out.

We can leave the old option in as deprecated option and add the new name
as new option, should be rather easy AFAIU,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Fri Sep  5 14:07:46 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 05 Sep 2014 16:07:46 +0200
Subject: [Openstack-docs] Modifying the 'front page' of the REST API
 Docs ?
In-Reply-To: <5058BED8BBDF5D4F898AD4366E6B36E02433EE14@ALA-MBB.corp.ad.wrs.com>
References: <5058BED8BBDF5D4F898AD4366E6B36E02433EE14@ALA-MBB.corp.ad.wrs.com>
Message-ID: <5409C3B2.5050107@suse.com>

On 09/05/2014 03:59 PM, Waines, Greg wrote:
> Does anyone know how to modify the front page of the PDF file that gets
> generated when building (mvn clean generate-sources) the rest api
> documentation ?
> 
>  
> 
> i.e. in order to be able to put company-specific branding on the document.

Check the clouddocs-maven-plugin, it handles AFAIU both rackspace and
openstack branding. There's a branding parameter in the pom.xml,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From annegentle at justwriteclick.com  Fri Sep  5 14:11:52 2014
From: annegentle at justwriteclick.com (Anne Gentle)
Date: Fri, 5 Sep 2014 09:11:52 -0500
Subject: [Openstack-docs] Modifying the 'front page' of the REST API
	Docs ?
In-Reply-To: <5409C3B2.5050107@suse.com>
References: <5058BED8BBDF5D4F898AD4366E6B36E02433EE14@ALA-MBB.corp.ad.wrs.com>
 <5409C3B2.5050107@suse.com>
Message-ID: <596F409F-297D-4C6C-9761-B399A452E8AA@justwriteclick.com>

Yep - you'll see we have a Rackspace branding output also that you can model after. 

Anne Gentle
Content Stacker
anne at openstack.org


> On Sep 5, 2014, at 9:07 AM, Andreas Jaeger <aj at suse.com> wrote:
> 
>> On 09/05/2014 03:59 PM, Waines, Greg wrote:
>> Does anyone know how to modify the front page of the PDF file that gets
>> generated when building (mvn clean generate-sources) the rest api
>> documentation ?
>> 
>> 
>> 
>> i.e. in order to be able to put company-specific branding on the document.
> 
> Check the clouddocs-maven-plugin, it handles AFAIU both rackspace and
> openstack branding. There's a branding parameter in the pom.xml,
> 
> Andreas
> -- 
> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs


From mkassawara at gmail.com  Fri Sep  5 18:14:57 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Fri, 5 Sep 2014 13:14:57 -0500
Subject: [Openstack-docs] Anyone familiar with ceilometer?
Message-ID: <CABA+jQqXFfZ_rOhNfYsAjL1CgcrVAnLa9HPRbJ90_cM7HBF+CA@mail.gmail.com>

I'm working on an installation guide improvements patch for ceilometer [1]
with Darren Chan and need someone familiar with the module/service to help
review it. I'm particularly concerned about the following issues:

1) What does Debian's debconf tool handle for MongoDB and ceilometer?
2) Why does SUSE include a unique step to configure the dispatcher (see
note in code)?

Can anyone help?

Thanks,
Matt

[1] https://review.openstack.org/#/c/118556/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140905/a81b8c57/attachment.html>

From aj at suse.com  Fri Sep  5 20:26:24 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 05 Sep 2014 22:26:24 +0200
Subject: [Openstack-docs] Proposal: Bug Squashing day on the 9th of
	September
In-Reply-To: <54083EFA.7000703@openstack.org>
References: <53E3D0F6.7040903@suse.com>
 <CAD0KtVEsCgzbQvbscdS-XsheVsRbQfKe2BtGwxYXL3jWDtxxrA@mail.gmail.com>
 <53EA6CB7.7070503@suse.com>
 <00f228af4c0d116d8e2cb92daba0fa87@objectif-libre.com>
 <54083EFA.7000703@openstack.org>
Message-ID: <540A1C70.9010709@suse.com>

On 09/04/2014 12:29 PM, Tom Fifield wrote:
> On 18/08/14 23:18, Gauvain Pocentek wrote:
>> Le 2014-08-12 21:36, Andreas Jaeger a ?crit :
>>> On 08/12/2014 05:29 PM, Anne Gentle wrote:
>>>> Thanks Andreas! Sounds like we have a good day and start. I'll add it to
>>>> this week's What's Up Doc and we'll plan for 9/9/14 bug squashing.
>>>
>>> I noticed that many bugs can be fixed with the autogeneration of our
>>> tables.
>>>
>>> Gauvain, could you do a run before the 9th, please? That way we might be
>>> able to close many bugs as fixed since the values are already in...
>>
>> Sure!
> 
> Hi,
> 
> I've done a fast triage run of the 'new' bugs in openstack-manuals. We
> now have 442 confirmed bugs (650+ if you count api-site too) ready for
> the bug day.

Tom, thanks a lot!
Andreas

> Found a couple of good low-hanging-fruit s, which have been tagged
> appropriately for newcomers.


-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Sun Sep  7 16:44:54 2014
From: aj at suse.com (Andreas Jaeger)
Date: Sun, 07 Sep 2014 18:44:54 +0200
Subject: [Openstack-docs] keystone "--user=nova" or "--user nova"?
Message-ID: <540C8B86.8020907@suse.com>

Do we have any preference for either of these:

(1)
keystone user-create --name=nova --pass=NOVA_PASS --email=nova at example.com
keystone user-role-add --user=nova --tenant=service --role=admin

or
(2)
keystone user-create --name neutron --pass NEUTRON_PASS --email
neutron at example.com
keystone user-role-add --user neutron --tenant service --role admin

Looking at the help output of client commands, the form without "=" is
preferred (see CLI Reference).

If we want to standardize, my proposal is for (2)

This is in reaction to:
https://review.openstack.org/#/c/119605/
https://bugs.launchpad.net/openstack-manuals/+bug/1366473

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From mkassawara at gmail.com  Sun Sep  7 17:02:53 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Sun, 7 Sep 2014 12:02:53 -0500
Subject: [Openstack-docs] keystone "--user=nova" or "--user nova"?
In-Reply-To: <540C8B86.8020907@suse.com>
References: <540C8B86.8020907@suse.com>
Message-ID: <CABA+jQqk4iPvYWOk_tRjC-pJUJAcQ0tR+zqXvSJwRAGozcgVjg@mail.gmail.com>

I opened a bug for this some time ago...

https://bugs.launchpad.net/openstack-manuals/+bug/1287890


On Sun, Sep 7, 2014 at 11:44 AM, Andreas Jaeger <aj at suse.com> wrote:

> Do we have any preference for either of these:
>
> (1)
> keystone user-create --name=nova --pass=NOVA_PASS --email=nova at example.com
> keystone user-role-add --user=nova --tenant=service --role=admin
>
> or
> (2)
> keystone user-create --name neutron --pass NEUTRON_PASS --email
> neutron at example.com
> keystone user-role-add --user neutron --tenant service --role admin
>
> Looking at the help output of client commands, the form without "=" is
> preferred (see CLI Reference).
>
> If we want to standardize, my proposal is for (2)
>
> This is in reaction to:
> https://review.openstack.org/#/c/119605/
> https://bugs.launchpad.net/openstack-manuals/+bug/1366473
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140907/7ac50c32/attachment.html>

From aj at suse.com  Sun Sep  7 19:17:43 2014
From: aj at suse.com (Andreas Jaeger)
Date: Sun, 07 Sep 2014 21:17:43 +0200
Subject: [Openstack-docs] keystone "--user=nova" or "--user nova"?
In-Reply-To: <CABA+jQqk4iPvYWOk_tRjC-pJUJAcQ0tR+zqXvSJwRAGozcgVjg@mail.gmail.com>
References: <540C8B86.8020907@suse.com>
 <CABA+jQqk4iPvYWOk_tRjC-pJUJAcQ0tR+zqXvSJwRAGozcgVjg@mail.gmail.com>
Message-ID: <540CAF57.8010302@suse.com>

On 09/07/2014 07:02 PM, Matt Kassawara wrote:
> I opened a bug for this some time ago...
> 
> https://bugs.launchpad.net/openstack-manuals/+bug/1287890

Seems there's agreement here so far, I've added this section to our
Conventions page:
https://wiki.openstack.org/wiki/Documentation/Conventions#Client_arguments:_.22--option_ARGUMENT.22

Let's wait another day another day before taking any action on this, I'd
like to give others the chance to chime in and comment on this,

Andreas

> 
> On Sun, Sep 7, 2014 at 11:44 AM, Andreas Jaeger <aj at suse.com
> <mailto:aj at suse.com>> wrote:
> 
>     Do we have any preference for either of these:
> 
>     (1)
>     keystone user-create --name=nova --pass=NOVA_PASS
>     --email=nova at example.com <mailto:nova at example.com>
>     keystone user-role-add --user=nova --tenant=service --role=admin
> 
>     or
>     (2)
>     keystone user-create --name neutron --pass NEUTRON_PASS --email
>     neutron at example.com <mailto:neutron at example.com>
>     keystone user-role-add --user neutron --tenant service --role admin
> 
>     Looking at the help output of client commands, the form without "=" is
>     preferred (see CLI Reference).
> 
>     If we want to standardize, my proposal is for (2)
> 
>     This is in reaction to:
>     https://review.openstack.org/#/c/119605/
>     https://bugs.launchpad.net/openstack-manuals/+bug/1366473
> 
>     Andreas
>     --
>      Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org
>     <http://opensuse.org>} Twitter/Identica: jaegerandi
>       SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>        GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>         GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> 
>     _______________________________________________
>     Openstack-docs mailing list
>     Openstack-docs at lists.openstack.org
>     <mailto:Openstack-docs at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
> 
> 
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 


-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From gauvain.pocentek at objectif-libre.com  Mon Sep  8 04:59:14 2014
From: gauvain.pocentek at objectif-libre.com (Gauvain Pocentek)
Date: Mon, 08 Sep 2014 06:59:14 +0200
Subject: [Openstack-docs]
 =?utf-8?q?Redirects_for_/trunk/install-guide=3F?=
In-Reply-To: <54047861.8020404@suse.com>
References: <54047861.8020404@suse.com>
Message-ID: <f22b5bd2c8fbcd5e69c3ac9d4749bf75@objectif-libre.com>

Le 2014-09-01 15:45, Andreas Jaeger a ?crit?:
> I suggest to not do any redirects for /trunk/install-guide - this is 
> the
> draft version and we should not do redirects for any change there.
> 
> https://review.openstack.org/#/c/118130
> 
> Does this work for you?

Works for me!

Did we reach an agreement on this? I'd like to make sure that 
everyone's OK with this decision before approving Joseph's ID changes 
patch (https://review.openstack.org/#/c/118097/).


Thanks,
Gauvain


From berendt at b1-systems.de  Mon Sep  8 07:13:59 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Mon, 08 Sep 2014 09:13:59 +0200
Subject: [Openstack-docs] keystone "--user=nova" or "--user nova"?
In-Reply-To: <540CAF57.8010302@suse.com>
References: <540C8B86.8020907@suse.com>
 <CABA+jQqk4iPvYWOk_tRjC-pJUJAcQ0tR+zqXvSJwRAGozcgVjg@mail.gmail.com>
 <540CAF57.8010302@suse.com>
Message-ID: <540D5737.3010008@b1-systems.de>

On 09/07/2014 09:17 PM, Andreas Jaeger wrote:
> Seems there's agreement here so far, I've added this section to our
> Conventions page:
> https://wiki.openstack.org/wiki/Documentation/Conventions#Client_arguments:_.22--option_ARGUMENT.22

+1 for "--option ARGUMENT".

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From anne at openstack.org  Mon Sep  8 12:53:45 2014
From: anne at openstack.org (Anne Gentle)
Date: Mon, 8 Sep 2014 07:53:45 -0500
Subject: [Openstack-docs] keystone "--user=nova" or "--user nova"?
In-Reply-To: <540C8B86.8020907@suse.com>
References: <540C8B86.8020907@suse.com>
Message-ID: <CAD0KtVHhkOOFLfcXKUcFPz8a8uedZ5Qn1T5RgiO=BHsjaqZX+w@mail.gmail.com>

On Sun, Sep 7, 2014 at 11:44 AM, Andreas Jaeger <aj at suse.com> wrote:

> Do we have any preference for either of these:
>
> (1)
> keystone user-create --name=nova --pass=NOVA_PASS --email=nova at example.com
> keystone user-role-add --user=nova --tenant=service --role=admin
>
> or
> (2)
> keystone user-create --name neutron --pass NEUTRON_PASS --email
> neutron at example.com
> keystone user-role-add --user neutron --tenant service --role admin
>
> Looking at the help output of client commands, the form without "=" is
> preferred (see CLI Reference).
>
> If we want to standardize, my proposal is for (2)
>

Thanks for proposing, I agree with 2 as well.


>
> This is in reaction to:
> https://review.openstack.org/#/c/119605/
> https://bugs.launchpad.net/openstack-manuals/+bug/1366473
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140908/b45ae61a/attachment.html>

From anne at openstack.org  Mon Sep  8 14:51:41 2014
From: anne at openstack.org (Anne Gentle)
Date: Mon, 8 Sep 2014 09:51:41 -0500
Subject: [Openstack-docs] Docs Bug Squash Day tomorrow, 9/9/14
Message-ID: <CAD0KtVEyeLJM8ghF7FuOWvM9LO8VsWwjW1c-yGMm33_v05sfgQ@mail.gmail.com>

Hi all,
We're planning a docs bug squash day tomorrow round-the-planet. With over
650 doc bugs there's plenty to go around. Last time we squashed over 100
bugs.

Refer to
https://wiki.openstack.org/wiki/Documentation/BugDay for details. We have
documentarians standing by in #openstack-doc.

Sometimes just finding a bug to work on is a challenge. Search for
Confirmed or Triaged, and make sure Nobody is assigned, then go to town!
openstack-manuals: http://is.gd/r07MXm
openstack-api-site: http://is.gd/Icn3h9

As a reminder, triaging bugs is super helpful. If you know the fix, but
can't set up the docs environment for any reason, please just comment in
the bug itself. Search for New bugs and triage those first.

Thanks -- looking forward to tomorrow (cleaning up still in anticipation)!
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140908/f73b765c/attachment.html>

From edgar.magana at workday.com  Mon Sep  8 16:20:24 2014
From: edgar.magana at workday.com (Edgar Magana)
Date: Mon, 8 Sep 2014 16:20:24 +0000
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
	team
In-Reply-To: <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
Message-ID: <D0332543.83DD%edgar.magana@workday.com>

Can you guys include me in any further discussions?
I want to help..

Thanks,

Edgar

From: Adam Lawson <alawson at aqorn.com<mailto:alawson at aqorn.com>>
Date: Tuesday, August 26, 2014 at 11:48 AM
To: Anne Gentle <anne at openstack.org<mailto:anne at openstack.org>>
Cc: David Medberry <david.medberry at canonical.com<mailto:david.medberry at canonical.com>>, Sriram Subramanian <sriram at sriramhere.com<mailto:sriram at sriramhere.com>>, "openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>" <openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>>, "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>>
Subject: Re: [Openstack-operators] High Availability Guide team


I'd be happy to participate as needed Anne.

On Aug 26, 2014 11:10 AM, "Anne Gentle" <anne at openstack.org<mailto:anne at openstack.org>> wrote:
Hi all,
Cross-posting to -docs and -operators.

At the Ops mid-cycle meetup this week, Matt Griffin, David Medberry, and Sriram Subramanian offered to start a review team for the High Availability Guide. It needs some updates and it's best if the review team works similar to the Security Guide -- subject matter experts working with core docs team members for reviews. So I'm proposing we pull it into its own repo just like the Security Guide. Any reasons not to? I think the next steps are:

1. Propose a patch to openstack/governance to show the repo is governed by the Docs program.
2. Propose a patch that sets up a separate review team starting with Matt, David, and Sriram. We think Emilien would be interested too, sound good? Any others? We can have members of openstack-docs-core as well, similar to the Security Guide.
3. Propose a patch that gets that guide building separately in a different repo.
4.  Start working on the four bugs already logged [1] and logged more as needed.

Any other subtasks? Any interested parties?

Thanks,
Anne

1. https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140908/8b8c4abe/attachment.html>

From berendt at b1-systems.de  Mon Sep  8 18:23:10 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Mon, 08 Sep 2014 20:23:10 +0200
Subject: [Openstack-docs] Minimum time before approving a review request
Message-ID: <540DF40E.1040609@b1-systems.de>

I would like to propose the introduction of a minimum time before
approving a new review request.

Example: https://review.openstack.org/#/c/119783/

Uploaded: Sep 8, 2014 4:59 PM
First +2: 6:10 PM
Second +2: 8:15 PM
Approval: 8:16 PM

I think we should wait at least 24 hours before approving a new review
request (exception: urgent or generated changes). This way everybody of
us has the chance to realize and review new review requests.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From anne at openstack.org  Mon Sep  8 18:30:46 2014
From: anne at openstack.org (Anne Gentle)
Date: Mon, 8 Sep 2014 13:30:46 -0500
Subject: [Openstack-docs] Minimum time before approving a review request
In-Reply-To: <540DF40E.1040609@b1-systems.de>
References: <540DF40E.1040609@b1-systems.de>
Message-ID: <CAD0KtVHYKcUWzsaepoDq3f+RZtYgjw2b8wPQsZUFMxtNaVM9Gw@mail.gmail.com>

On Mon, Sep 8, 2014 at 1:23 PM, Christian Berendt <berendt at b1-systems.de>
wrote:

> I would like to propose the introduction of a minimum time before
> approving a new review request.
>
> Example: https://review.openstack.org/#/c/119783/
>
> Uploaded: Sep 8, 2014 4:59 PM
> First +2: 6:10 PM
> Second +2: 8:15 PM
> Approval: 8:16 PM
>
> I think we should wait at least 24 hours before approving a new review
> request (exception: urgent or generated changes). This way everybody of
> us has the chance to realize and review new review requests.
>
>
Interesting proposal, we did not address in
https://wiki.openstack.org/wiki/Documentation/ReviewGuidelines -- my
feeling is that we can't all review all patches so it's better to not
enforce a minimum wait time. The impatience people have with our reviews
should be reversed and we shouldn't have a policy of an enforced wait time.

To me, it's preferred to have hundreds of patches go through efficiently
rather than ensure everyone sees every patch.

Just my thinking though, would love to hear what others have to say.

Anne


> Christian.
>
> --
> Christian Berendt
> Cloud Solution Architect
> Mail: berendt at b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140908/805cc4f8/attachment-0001.html>

From nchase at mirantis.com  Mon Sep  8 18:41:43 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Mon, 08 Sep 2014 14:41:43 -0400
Subject: [Openstack-docs] Minimum time before approving a review request
In-Reply-To: <CAD0KtVHYKcUWzsaepoDq3f+RZtYgjw2b8wPQsZUFMxtNaVM9Gw@mail.gmail.com>
References: <540DF40E.1040609@b1-systems.de>
 <CAD0KtVHYKcUWzsaepoDq3f+RZtYgjw2b8wPQsZUFMxtNaVM9Gw@mail.gmail.com>
Message-ID: <540DF867.8050601@mirantis.com>


On 9/8/2014 2:30 PM, Anne Gentle wrote:
>
> On Mon, Sep 8, 2014 at 1:23 PM, Christian Berendt 
> <berendt at b1-systems.de <mailto:berendt at b1-systems.de>> wrote:
>
>     I would like to propose the introduction of a minimum time before
>     approving a new review request.
>
>     Example: https://review.openstack.org/#/c/119783/
>
>     Uploaded: Sep 8, 2014 4:59 PM
>     First +2: 6:10 PM
>     Second +2: 8:15 PM
>     Approval: 8:16 PM
>
>     I think we should wait at least 24 hours before approving a new review
>     request (exception: urgent or generated changes). This way
>     everybody of
>     us has the chance to realize and review new review requests.
>
>
> Interesting proposal, we did not address in 
> https://wiki.openstack.org/wiki/Documentation/ReviewGuidelines -- my 
> feeling is that we can't all review all patches so it's better to not 
> enforce a minimum wait time. The impatience people have with our 
> reviews should be reversed and we shouldn't have a policy of an 
> enforced wait time.
>
> To me, it's preferred to have hundreds of patches go through 
> efficiently rather than ensure everyone sees every patch.
>
> Just my thinking though, would love to hear what others have to say.
>

I think that it's a good thought to make sure that patches have enough 
oversight, but it's unrealistic to have "everybody" look at a patch; 
there's just not enough time, as evidenced by the backlog we already 
have. If a patch goes through and someone has a concern, opening a new 
bug is just a button-click away.

I also agree that people (all over OpenStack, not just in Docs) are 
already frustrated enough with the review process. ENSURING that it 
takes a day will only make things worse, I would think.

But perhaps if there's a patch that people are concerned about -- say 
something major is going on -- there's a way for us to flag it, or maybe 
just to have the cores to +1 it temporarily just to show that they're in 
favor, while it's being further reviewed?

----  Nick

-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
<http://openstacksv.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140908/899b7e9d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140908/899b7e9d/attachment.png>

From mkassawara at gmail.com  Mon Sep  8 18:57:15 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Mon, 8 Sep 2014 13:57:15 -0500
Subject: [Openstack-docs] Minimum time before approving a review request
In-Reply-To: <540DF867.8050601@mirantis.com>
References: <540DF40E.1040609@b1-systems.de>
 <CAD0KtVHYKcUWzsaepoDq3f+RZtYgjw2b8wPQsZUFMxtNaVM9Gw@mail.gmail.com>
 <540DF867.8050601@mirantis.com>
Message-ID: <CABA+jQpmCCr-MZ-XfMG1iKU9jZ=aPrPME7+Sdpw672Ay-MQnQA@mail.gmail.com>

I agree with Anne and Nick. In the case of questionable content, most of us
tag other reviewers and wait a certain amount of time for them to review
the patch. Also, larger patches already tend to remain in the review queue
for a reasonable amount of time.

On Mon, Sep 8, 2014 at 1:41 PM, Nicholas Chase <nchase at mirantis.com> wrote:

>
> On 9/8/2014 2:30 PM, Anne Gentle wrote:
>
>
> On Mon, Sep 8, 2014 at 1:23 PM, Christian Berendt <berendt at b1-systems.de>
> wrote:
>
>> I would like to propose the introduction of a minimum time before
>> approving a new review request.
>>
>> Example: https://review.openstack.org/#/c/119783/
>>
>> Uploaded: Sep 8, 2014 4:59 PM
>> First +2: 6:10 PM
>> Second +2: 8:15 PM
>> Approval: 8:16 PM
>>
>> I think we should wait at least 24 hours before approving a new review
>> request (exception: urgent or generated changes). This way everybody of
>> us has the chance to realize and review new review requests.
>>
>>
>  Interesting proposal, we did not address in
> https://wiki.openstack.org/wiki/Documentation/ReviewGuidelines -- my
> feeling is that we can't all review all patches so it's better to not
> enforce a minimum wait time. The impatience people have with our reviews
> should be reversed and we shouldn't have a policy of an enforced wait time.
>
>  To me, it's preferred to have hundreds of patches go through efficiently
> rather than ensure everyone sees every patch.
>
>  Just my thinking though, would love to hear what others have to say.
>
>
> I think that it's a good thought to make sure that patches have enough
> oversight, but it's unrealistic to have "everybody" look at a patch;
> there's just not enough time, as evidenced by the backlog we already have.
> If a patch goes through and someone has a concern, opening a new bug is
> just a button-click away.
>
> I also agree that people (all over OpenStack, not just in Docs) are
> already frustrated enough with the review process. ENSURING that it takes a
> day will only make things worse, I would think.
>
> But perhaps if there's a patch that people are concerned about -- say
> something major is going on -- there's a way for us to flag it, or maybe
> just to have the cores to +1 it temporarily just to show that they're in
> favor, while it's being further reviewed?
>
> ----  Nick
>
> --
> Nick Chase
> 1-650-567-5640
> Technical Marketing Manager, Mirantis
> Editor, OpenStack:Now
>  <http://openstacksv.com>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140908/6a8b1dbf/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140908/6a8b1dbf/attachment-0001.png>

From aj at suse.com  Mon Sep  8 19:19:26 2014
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 08 Sep 2014 21:19:26 +0200
Subject: [Openstack-docs] Minimum time before approving a review request
In-Reply-To: <CABA+jQpmCCr-MZ-XfMG1iKU9jZ=aPrPME7+Sdpw672Ay-MQnQA@mail.gmail.com>
References: <540DF40E.1040609@b1-systems.de>
 <CAD0KtVHYKcUWzsaepoDq3f+RZtYgjw2b8wPQsZUFMxtNaVM9Gw@mail.gmail.com>
 <540DF867.8050601@mirantis.com>
 <CABA+jQpmCCr-MZ-XfMG1iKU9jZ=aPrPME7+Sdpw672Ay-MQnQA@mail.gmail.com>
Message-ID: <540E013E.705@suse.com>

On 09/08/2014 08:57 PM, Matt Kassawara wrote:
> I agree with Anne and Nick. In the case of questionable content, most of
> us tag other reviewers and wait a certain amount of time for them to
> review the patch. Also, larger patches already tend to remain in the
> review queue for a reasonable amount of time.
> 

For patches where we need more discussion, most of us add a comment
stating so.

Having a quick turnaround is IMHO one of our great benefits great and
gives contributors a really good experience.

If something goes in that's wrong, we can also easily revert ;)

I review many patches - and I'm glad for those that I never see because
others reviewed them before me ;)

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From rbowen at redhat.com  Mon Sep  8 19:30:04 2014
From: rbowen at redhat.com (Rich Bowen)
Date: Mon, 08 Sep 2014 15:30:04 -0400
Subject: [Openstack-docs] Minimum time before approving a review request
In-Reply-To: <540DF40E.1040609@b1-systems.de>
References: <540DF40E.1040609@b1-systems.de>
Message-ID: <540E03BC.6070303@redhat.com>


On 09/08/2014 02:23 PM, Christian Berendt wrote:
> I would like to propose the introduction of a minimum time before
> approving a new review request.
>
> Example: https://review.openstack.org/#/c/119783/
>
> Uploaded: Sep 8, 2014 4:59 PM
> First +2: 6:10 PM
> Second +2: 8:15 PM
> Approval: 8:16 PM
>
> I think we should wait at least 24 hours before approving a new review
> request (exception: urgent or generated changes). This way everybody of
> us has the chance to realize and review new review requests.
>
> Christian.
>
I'm curious what problem you're trying to solve with this. To me, it 
looks like responsiveness to a patch and quick turnaround. What does it 
look like to you? Do you feel it had insufficient oversight?

I've never been part of an Open Source project where anyone felt that we 
should take *longer* to close tickets or respond to patches.

-- 
Rich Bowen - rbowen at redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/



From tom at openstack.org  Tue Sep  9 00:37:47 2014
From: tom at openstack.org (Tom Fifield)
Date: Tue, 09 Sep 2014 08:37:47 +0800
Subject: [Openstack-docs] Minimum time before approving a review request
In-Reply-To: <540E013E.705@suse.com>
References: <540DF40E.1040609@b1-systems.de>
 <CAD0KtVHYKcUWzsaepoDq3f+RZtYgjw2b8wPQsZUFMxtNaVM9Gw@mail.gmail.com>
 <540DF867.8050601@mirantis.com>
 <CABA+jQpmCCr-MZ-XfMG1iKU9jZ=aPrPME7+Sdpw672Ay-MQnQA@mail.gmail.com>
 <540E013E.705@suse.com>
Message-ID: <540E4BDB.5090507@openstack.org>

On 09/09/14 03:19, Andreas Jaeger wrote:
> On 09/08/2014 08:57 PM, Matt Kassawara wrote:
>> I agree with Anne and Nick. In the case of questionable content, most of
>> us tag other reviewers and wait a certain amount of time for them to
>> review the patch. Also, larger patches already tend to remain in the
>> review queue for a reasonable amount of time.
>>
> 
> For patches where we need more discussion, most of us add a comment
> stating so.
> 
> Having a quick turnaround is IMHO one of our great benefits great and
> gives contributors a really good experience.
> 
> If something goes in that's wrong, we can also easily revert ;)
> 
> I review many patches - and I'm glad for those that I never see because
> others reviewed them before me ;)

+1

This was discussed in the python projects and the conclusion was: don't
have a minimum time before approving a review request. Instead, common
sense and reverts as needed.

Regards,

Tom



From sayali.92720 at gmail.com  Tue Sep  9 18:27:19 2014
From: sayali.92720 at gmail.com (Sayali Lunkad)
Date: Tue, 9 Sep 2014 23:57:19 +0530
Subject: [Openstack-docs] Audio Visual Content and Structure for
	training-guides
Message-ID: <CAObJ2cEh1SOM6ZwvT4i1WnJv3B4apDB8NvF=qfxkmc54U7vZag@mail.gmail.com>

Hi,

This is the etherpad link to discuss the structure and content of the Audio
Visual content to be included in the training-guides.
https://etherpad.openstack.org/p/openstck-training-guides%28Audio_Visual_Content%29
Please feel free to add or edit the content here.

Regards,
Sayali.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140909/bde22f12/attachment.html>

From anne at openstack.org  Wed Sep 10 15:03:19 2014
From: anne at openstack.org (Anne Gentle)
Date: Wed, 10 Sep 2014 10:03:19 -0500
Subject: [Openstack-docs] What's up doc? Sept. 10, 2014
Message-ID: <CAD0KtVH48mAnVsfNwCGPs89LMtpVB6Rqn_wbrJ3dv0sychgW7Q@mail.gmail.com>

Bug squash day worked well on 9/9 -- squashing and triaging bugs, bringing
the openstack-manuals backlog to about 400, with 50 in progress even now!
The openstack-api-site backlog went to about 200 with 15 in progress. We
also had some fairly new docs contributors join in -- thank you everyone
who helped out.

__In review and merged this past week__

This week was about bug squashing!

__High priority doc work__

Install Guide testing starts in earnest once packages are available and
with feature freeze this should be in the next week or so. We've been
keeping up with both CLI and config reference patches at milestone releases.

__Ongoing doc work__

The separate Networking Guide is still ongoing. Nick Chase has been
interviewing contractors to pick up the work that still needs to be done,
thank you Nick. Shaun McCance has moved to other contracts, thank you Shaun
for your efforts.

__New incoming doc requests__

Security Guide authors, there is interest in specializing your book by
Cisco, and I wanted to let everyone know how exciting this is. I've asked
them to look at the bug backlog and see what they could contribute upstream
also, and they're willing and interested. The vision is that upstream docs
can be reused and repurposed so I'm happy to see this vision become
reality. I'm finding out if there are any particular mechanics needed so
stay tuned.

__Doc tools updates__

We should have a new release of the clouddocs-maven-plugin in the next 2
weeks with these features, mostly API reference-focused:
Fix css padding-top for Rackspace output https://review.openstack.org/108156
Add the title of the service to API reference
https://review.openstack.org/107768
Add fanatiguy to Rackspace API Ref https://review.openstack.org/112703
Add support for yaml syntax highlighting:
https://review.openstack.org/#/c/111219/1
Allow error phrase to be listed with response code:
https://review.openstack.org/106173

__Other doc news__

I've been clarifying what it means to be incubated from a documentation
perspective on this wiki page. Most recently the Manila project was
incubated and they're looking into how docs are incubated and integrated.

The training team will discuss whether a separate program incubation
application makes sense for them at their next team meeting, held Mondays
at 12:00 Central in #openstack-meeting.

An end user interest group has been having a lot of discussion on the
user-committee mailing list. I wanted to be sure docs people know that the
Foundation is seeking input on developer.openstack.org and looking for an
app ecosystem community manager. If you know someone doing great work on
cloud apps on OpenStack, please join us on that mailing list thread and let
us know.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140910/e33785fa/attachment.html>

From mkassawara at gmail.com  Wed Sep 10 18:17:52 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Wed, 10 Sep 2014 13:17:52 -0500
Subject: [Openstack-docs] Installation guide updates for Juno
Message-ID: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>

Ubuntu recently began offering pre-release Juno packages [1] and I
successfully built a three-node "core services" environment using them.
Let's discuss the potential changes...

1) So far, updating the OpenStack services chapters of the installation
guide mostly involves some configuration file changes, removing old
workarounds, and probably adding new workarounds. Should we use a bug or a
blueprint for these issues? In either case, I recommend uploading separate
patches for each service.

2) Neutron supports distributed virtual routers (DVR) and I'm sure people
want instructions for deploying them. However, DVR introduces more
complexity to already difficult networking concepts and requires
architectural changes to fully configure and demonstrate. At least for
Juno, I recommend keeping the legacy architecture and adding instructions
for deploying DVR to the networking or admin guides.

3) Open vSwitch adds another level of complexity to already difficult
networking concepts, particularly with troubleshooting. Linux Bridge
provides a reliable alternative that reduces complexity, but DVR doesn't
support it. Should we add instructions for deploying Linux Bridge as an
alternative to Open vSwitch?

4) The neutron external network (ext-net) "magically" works although we
don't explicitly configure support for flat networks. For sanity, we should
probably adjust the configuration to support one flat network and adjust
the initial network instructions to use it as a flat provider network.

5) I'm seeing more deployments moving from novnc to spice consoles. Should
we configure spice instead of novnc?

6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu 14.04
offers MariaDB 5.5 which more or less clones MySQL 5.5 including the
configuration files. I suspect RHEL 7, Fedora, and other RPM distributions
also offer MariaDB packages. Should we change all distributions to MariaDB?

[1] https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/juno-staging

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140910/84e89f12/attachment.html>

From chris.friesen at windriver.com  Wed Sep 10 17:43:16 2014
From: chris.friesen at windriver.com (Chris Friesen)
Date: Wed, 10 Sep 2014 11:43:16 -0600
Subject: [Openstack-docs] Is comment about active/active RabbitMQ config
	still a valid concern?
Message-ID: <54108DB4.1030005@windriver.com>

Hi,

I'm trying to figure out the recommended configuration for RabbitMQ for 
use by OpenStack.

At 
"http://docs.openstack.org/high-availability-guide/content/s-rabbitmq.html" 
it says,

"There is an alternative method of configuring RabbitMQ for high 
availability. That approach, known as active-active mirrored queues, 
happens to be the one preferred by the RabbitMQ developers?however it 
has shown less than ideal consistency and reliability in OpenStack 
clusters. Thus, at the time of writing, the Pacemaker/DRBD based 
approach remains the recommended one for OpenStack environments, 
although this may change in the near future as RabbitMQ active-active 
mirrored queues mature."

In the same document at 
"http://docs.openstack.org/high-availability-guide/content/_configure_rabbitmq.html" 
it has instructions on how to configure rabbitmq as active/active with 
mirrored queues.

Is the comment about active/standby being preferred still current or is 
it stale?

Which is the recommended configuration?

Thanks,
Chris


From gauvain.pocentek at objectif-libre.com  Wed Sep 10 19:41:59 2014
From: gauvain.pocentek at objectif-libre.com (Gauvain Pocentek)
Date: Wed, 10 Sep 2014 21:41:59 +0200
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
Message-ID: <7fffa3b284fd5fdac72d0fda6f6d4414@objectif-libre.com>

Le 2014-09-10 20:17, Matt Kassawara a ?crit?:
> Ubuntu recently began offering pre-release Juno packages [1] and I
> successfully built a three-node "core services" environment using
> them. Let's discuss the potential changes...
> 
> 1) So far, updating the OpenStack services chapters of the
> installation guide mostly involves some configuration file changes,
> removing old workarounds, and probably adding new workarounds. Should
> we use a bug or a blueprint for these issues? In either case, I
> recommend uploading separate patches for each service.

I wouldn't use BPs for this, and multiple bugs will probably be too 
much administrative work. Maybe just 1 bug to track the progress?

> 
> 2) Neutron supports distributed virtual routers (DVR) and I'm sure
> people want instructions for deploying them. However, DVR introduces
> more complexity to already difficult networking concepts and requires
> architectural changes to fully configure and demonstrate. At least for
> Juno, I recommend keeping the legacy architecture and adding
> instructions for deploying DVR to the networking or admin guides.

+1

> 
> 3) Open vSwitch adds another level of complexity to already difficult
> networking concepts, particularly with troubleshooting. Linux Bridge
> provides a reliable alternative that reduces complexity, but DVR
> doesn't support it. Should we add instructions for deploying Linux
> Bridge as an alternative to Open vSwitch?

I think that we should keep OVS. I'm not sure it is more complex to set 
it up than linux bridge (maybe I'm completely wrong).

> 
> 4) The neutron external network (ext-net) "magically" works although
> we don't explicitly configure support for flat networks. For sanity,
> we should probably adjust the configuration to support one flat
> network and adjust the initial network instructions to use it as a
> flat provider network.

+1 for flat network. IIRC we had instructions to set this up in havana, 
along other networking setup solutions.

> 
> 5) I'm seeing more deployments moving from novnc to spice consoles.
> Should we configure spice instead of novnc?

I'm fine with either one. The concept for the setup are similar.

> 
> 6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu
> 14.04 offers MariaDB 5.5 which more or less clones MySQL 5.5 including
> the configuration files. I suspect RHEL 7, Fedora, and other RPM
> distributions also offer MariaDB packages. Should we change all
> distributions to MariaDB?

I've not used Maria yet, so I really don't know  what's best here.


Gauvain


From phil.hopkins at rackspace.com  Wed Sep 10 19:51:57 2014
From: phil.hopkins at rackspace.com (Phil Hopkins)
Date: Wed, 10 Sep 2014 19:51:57 +0000
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
Message-ID: <FBC99830465C784CAF93C211A517C0F493E245F1@ORD1EXD03.RACKSPACE.CORP>

Matt,

My thoughts:
1. I believe bus will be easier to track but it means for a lot of bugs to be created.

2. For now lets keep the DVR stuff in the Networking/admin guide. It avoids massive changes to the install guides - for now.

3. I really like using Linux Bridge over OVS, but again I think minimizing changes to the install guide will help use get something usable by Juno release. Lets look at adding that material later.

4. make it flat.

5. Again my preference is to get Juno install done first. Add new material later. SPICE would be a ggod change but lets roll that out later. novnc woks fine for now.

 6. We need to go to MariaDB (RHEL7 only has MariaDB). Again lets plan on moving but it doesn't need to be done on first release.

I know this seems like I am in favor of putting everything off, but I want us to have a workable manual out on Juno release time. I don't see any of these items as necessary on release date.

[X][X][X][X]
Phil Hopkins RHCA CMDBA
Openstack Instructor
Rackspace Hostingtm
(210) 312-3584
________________________________
From: Matt Kassawara [mkassawara at gmail.com]
Sent: Wednesday, September 10, 2014 1:17 PM
To: openstack-docs at lists.openstack.org
Subject: [Openstack-docs] Installation guide updates for Juno

Ubuntu recently began offering pre-release Juno packages [1] and I successfully built a three-node "core services" environment using them. Let's discuss the potential changes...

1) So far, updating the OpenStack services chapters of the installation guide mostly involves some configuration file changes, removing old workarounds, and probably adding new workarounds. Should we use a bug or a blueprint for these issues? In either case, I recommend uploading separate patches for each service.

2) Neutron supports distributed virtual routers (DVR) and I'm sure people want instructions for deploying them. However, DVR introduces more complexity to already difficult networking concepts and requires architectural changes to fully configure and demonstrate. At least for Juno, I recommend keeping the legacy architecture and adding instructions for deploying DVR to the networking or admin guides.

3) Open vSwitch adds another level of complexity to already difficult networking concepts, particularly with troubleshooting. Linux Bridge provides a reliable alternative that reduces complexity, but DVR doesn't support it. Should we add instructions for deploying Linux Bridge as an alternative to Open vSwitch?

4) The neutron external network (ext-net) "magically" works although we don't explicitly configure support for flat networks. For sanity, we should probably adjust the configuration to support one flat network and adjust the initial network instructions to use it as a flat provider network.

5) I'm seeing more deployments moving from novnc to spice consoles. Should we configure spice instead of novnc?

6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu 14.04 offers MariaDB 5.5 which more or less clones MySQL 5.5 including the configuration files. I suspect RHEL 7, Fedora, and other RPM distributions also offer MariaDB packages. Should we change all distributions to MariaDB?

[1] https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/juno-staging

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140910/b78d842a/attachment-0001.html>

From sgordon at redhat.com  Wed Sep 10 19:52:57 2014
From: sgordon at redhat.com (Steve Gordon)
Date: Wed, 10 Sep 2014 15:52:57 -0400 (EDT)
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
Message-ID: <1288199568.10929761.1410378777669.JavaMail.zimbra@redhat.com>

----- Original Message -----
> From: "Matt Kassawara" <mkassawara at gmail.com>
> To: openstack-docs at lists.openstack.org
> 
> Ubuntu recently began offering pre-release Juno packages [1] and I
> successfully built a three-node "core services" environment using them.
> Let's discuss the potential changes...
> 
> 1) So far, updating the OpenStack services chapters of the installation
> guide mostly involves some configuration file changes, removing old
> workarounds, and probably adding new workarounds. Should we use a bug or a
> blueprint for these issues? In either case, I recommend uploading separate
> patches for each service.
> 
> 2) Neutron supports distributed virtual routers (DVR) and I'm sure people
> want instructions for deploying them. However, DVR introduces more
> complexity to already difficult networking concepts and requires
> architectural changes to fully configure and demonstrate. At least for
> Juno, I recommend keeping the legacy architecture and adding instructions
> for deploying DVR to the networking or admin guides.
> 
> 3) Open vSwitch adds another level of complexity to already difficult
> networking concepts, particularly with troubleshooting. Linux Bridge
> provides a reliable alternative that reduces complexity, but DVR doesn't
> support it. Should we add instructions for deploying Linux Bridge as an
> alternative to Open vSwitch?
> 
> 4) The neutron external network (ext-net) "magically" works although we
> don't explicitly configure support for flat networks. For sanity, we should
> probably adjust the configuration to support one flat network and adjust
> the initial network instructions to use it as a flat provider network.
> 
> 5) I'm seeing more deployments moving from novnc to spice consoles. Should
> we configure spice instead of novnc?
>
> 6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu 14.04
> offers MariaDB 5.5 which more or less clones MySQL 5.5 including the
> configuration files. I suspect RHEL 7, Fedora, and other RPM distributions
> also offer MariaDB packages. Should we change all distributions to MariaDB?
> 
> [1] https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/juno-staging

RDO and RHELOSP actually already moved to mariadb 5.5 in the Icehouse-based releases.

-Steve


From nchase at mirantis.com  Wed Sep 10 23:47:47 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Wed, 10 Sep 2014 19:47:47 -0400
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
Message-ID: <5410E323.7010507@mirantis.com>


On 9/10/2014 2:17 PM, Matt Kassawara wrote:
> Ubuntu recently began offering pre-release Juno packages [1] and I 
> successfully built a three-node "core services" environment using 
> them. Let's discuss the potential changes...
>
> 1) So far, updating the OpenStack services chapters of the 
> installation guide mostly involves some configuration file changes, 
> removing old workarounds, and probably adding new workarounds. Should 
> we use a bug or a blueprint for these issues? In either case, I 
> recommend uploading separate patches for each service.

I think we need separate bugs for each task so that we can have small 
patches that can be finished and merged.  That means multiple bugs, so 
I'm for blueprints to organize them.  Nothing fancy, just something to 
help us keep track.

> 2) Neutron supports distributed virtual routers (DVR) and I'm sure 
> people want instructions for deploying them. However, DVR introduces 
> more complexity to already difficult networking concepts and requires 
> architectural changes to fully configure and demonstrate. At least for 
> Juno, I recommend keeping the legacy architecture and adding 
> instructions for deploying DVR to the networking or admin guides.

+1

> 3) Open vSwitch adds another level of complexity to already difficult 
> networking concepts, particularly with troubleshooting. Linux Bridge 
> provides a reliable alternative that reduces complexity, but DVR 
> doesn't support it. Should we add instructions for deploying Linux 
> Bridge as an alternative to Open vSwitch?

If we leave DVR out of the install the fact that it doesn't support 
Linux Bridge doesn't matter, methinks.  That said, I'm for making as few 
changes to the install guides as necessary to get us to Juno.

> 4) The neutron external network (ext-net) "magically" works although 
> we don't explicitly configure support for flat networks. For sanity, 
> we should probably adjust the configuration to support one flat 
> network and adjust the initial network instructions to use it as a 
> flat provider network.

+1

> 5) I'm seeing more deployments moving from novnc to spice consoles. 
> Should we configure spice instead of novnc?

I think it's worth thinking about but I would consider it a lower 
priority than just making sure everything works as-is.

> 6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu 
> 14.04 offers MariaDB 5.5 which more or less clones MySQL 5.5 including 
> the configuration files. I suspect RHEL 7, Fedora, and other RPM 
> distributions also offer MariaDB packages. Should we change all 
> distributions to MariaDB?

+1

----  Nick

>
> [1] 
> https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/juno-staging 
> <https://launchpad.net/%7Eubuntu-cloud-archive/+archive/ubuntu/juno-staging>
>
> Matt
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
<http://openstacksv.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140910/cec62a3c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140910/cec62a3c/attachment.png>

From aj at suse.com  Thu Sep 11 07:13:40 2014
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 11 Sep 2014 09:13:40 +0200
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
Message-ID: <54114BA4.1000304@suse.com>

On 09/10/2014 08:17 PM, Matt Kassawara wrote:
> Ubuntu recently began offering pre-release Juno packages [1] and I
> successfully built a three-node "core services" environment using them.
> Let's discuss the potential changes...
> 
> 1) So far, updating the OpenStack services chapters of the installation
> guide mostly involves some configuration file changes, removing old
> workarounds, and probably adding new workarounds. Should we use a bug or
> a blueprint for these issues? In either case, I recommend uploading
> separate patches for each service.

Separate patch for each service is fine.

Blueprint or bug is not needed IMHO.

If you really want one, create a *single* bug that covers everything.

> 2) Neutron supports distributed virtual routers (DVR) and I'm sure
> people want instructions for deploying them. However, DVR introduces
> more complexity to already difficult networking concepts and requires
> architectural changes to fully configure and demonstrate. At least for
> Juno, I recommend keeping the legacy architecture and adding
> instructions for deploying DVR to the networking or admin guides.

Let's mature DVR a bit first.

> 3) Open vSwitch adds another level of complexity to already difficult
> networking concepts, particularly with troubleshooting. Linux Bridge
> provides a reliable alternative that reduces complexity, but DVR doesn't
> support it. Should we add instructions for deploying Linux Bridge as an
> alternative to Open vSwitch?

This can be done later at any time, it should be lower priority.

> 4) The neutron external network (ext-net) "magically" works although we
> don't explicitly configure support for flat networks. For sanity, we
> should probably adjust the configuration to support one flat network and
> adjust the initial network instructions to use it as a flat provider
> network.
> 
> 5) I'm seeing more deployments moving from novnc to spice consoles.
> Should we configure spice instead of novnc?

I don't think that's really needed.

> 6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu
> 14.04 offers MariaDB 5.5 which more or less clones MySQL 5.5 including
> the configuration files. I suspect RHEL 7, Fedora, and other RPM
> distributions also offer MariaDB packages. Should we change all
> distributions to MariaDB?

openSUSE is using MariaDB already, SLES is still with MySQL but will be
MariaDB with SLES 12 (for Kilo).

Andreas

> [1] https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/juno-staging
> 
> Matt
> 
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 


-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Thu Sep 11 07:15:04 2014
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 11 Sep 2014 09:15:04 +0200
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <5410E323.7010507@mirantis.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
 <5410E323.7010507@mirantis.com>
Message-ID: <54114BF8.7070400@suse.com>

On 09/11/2014 01:47 AM, Nicholas Chase wrote:
> 
> On 9/10/2014 2:17 PM, Matt Kassawara wrote:
>> Ubuntu recently began offering pre-release Juno packages [1] and I
>> successfully built a three-node "core services" environment using
>> them. Let's discuss the potential changes...
>>
>> 1) So far, updating the OpenStack services chapters of the
>> installation guide mostly involves some configuration file changes,
>> removing old workarounds, and probably adding new workarounds. Should
>> we use a bug or a blueprint for these issues? In either case, I
>> recommend uploading separate patches for each service.
> 
> I think we need separate bugs for each task so that we can have small
> patches that can be finished and merged.  That means multiple bugs, so
> I'm for blueprints to organize them.  Nothing fancy, just something to
> help us keep track.

If you need something to keep track, we can also use an etherpad or wiki
page.

I consider a separate bug for each issue a lot of overhead,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From berendt at b1-systems.de  Thu Sep 11 07:48:50 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Thu, 11 Sep 2014 09:48:50 +0200
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
Message-ID: <541153E2.3000103@b1-systems.de>

On 09/10/2014 08:17 PM, Matt Kassawara wrote:
> 3) Open vSwitch adds another level of complexity to already difficult
> networking concepts, particularly with troubleshooting. Linux Bridge
> provides a reliable alternative that reduces complexity, but DVR doesn't
> support it. Should we add instructions for deploying Linux Bridge as an
> alternative to Open vSwitch?

As an alternative I would like to see linux bridges. But please do not
remove instructions for Open vSwitch.

> 5) I'm seeing more deployments moving from novnc to spice consoles.
> Should we configure spice instead of novnc?

As an alternative I would like to see Spice. But I think we should not
remove instructions for noVNC.

> 6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu
> 14.04 offers MariaDB 5.5 which more or less clones MySQL 5.5 including
> the configuration files. I suspect RHEL 7, Fedora, and other RPM
> distributions also offer MariaDB packages. Should we change all
> distributions to MariaDB?

We should move to MariaDB. Because SLE11 does not include MariaDB we
have to wait for SLE12 (at least for SLE).

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From anne at openstack.org  Thu Sep 11 15:41:49 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 11 Sep 2014 10:41:49 -0500
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
Message-ID: <CAD0KtVHcfhLX=gKPOu7rorpmriByjhMMza33pnE_+9Y_mHLaOw@mail.gmail.com>

On Wed, Sep 10, 2014 at 1:17 PM, Matt Kassawara <mkassawara at gmail.com>
wrote:

> Ubuntu recently began offering pre-release Juno packages [1] and I
> successfully built a three-node "core services" environment using them.
> Let's discuss the potential changes...
>
> 1) So far, updating the OpenStack services chapters of the installation
> guide mostly involves some configuration file changes, removing old
> workarounds, and probably adding new workarounds. Should we use a bug or a
> blueprint for these issues? In either case, I recommend uploading separate
> patches for each service.
>
> First off, so glad you're paying attention and have the eye for this work.

Definitely separate patches will be easier to review. I think you should
track with the Juno install guide blueprint at
https://blueprints.launchpad.net/openstack-manuals/+spec/installation-guide-improvements
-- sound good?


> 2) Neutron supports distributed virtual routers (DVR) and I'm sure people
> want instructions for deploying them. However, DVR introduces more
> complexity to already difficult networking concepts and requires
> architectural changes to fully configure and demonstrate. At least for
> Juno, I recommend keeping the legacy architecture and adding instructions
> for deploying DVR to the networking or admin guides.
>
>
Yeah, let's keep DVR in a separate guide. Install Guide is meant for happy
path, get-an-instance-bootable architecture.


> 3) Open vSwitch adds another level of complexity to already difficult
> networking concepts, particularly with troubleshooting. Linux Bridge
> provides a reliable alternative that reduces complexity, but DVR doesn't
> support it. Should we add instructions for deploying Linux Bridge as an
> alternative to Open vSwitch?
>
>
I wouldn't add it to the install guide.

What I do hear from others is that OVS is not easily understood because
it's less deployed, but that's just rumor really. Still, now's the perfect
time to ask the question and visit the answer.


> 4) The neutron external network (ext-net) "magically" works although we
> don't explicitly configure support for flat networks. For sanity, we should
> probably adjust the configuration to support one flat network and adjust
> the initial network instructions to use it as a flat provider network.
>
>
Man it would be great to support one flat network. Is that then making for
three networking architectures? I'm not opposed, just making sure I
understand.


> 5) I'm seeing more deployments moving from novnc to spice consoles. Should
> we configure spice instead of novnc?
>
>
Nah, less change is better for that. More NoVNC in the field also I believe.


> 6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu 14.04
> offers MariaDB 5.5 which more or less clones MySQL 5.5 including the
> configuration files. I suspect RHEL 7, Fedora, and other RPM distributions
> also offer MariaDB packages. Should we change all distributions to MariaDB?
>

It will make maintenance easier, and sounds like it's possible with Kilo,
but not yet with Juno. So... sorry.

To summarize:
Use
https://blueprints.launchpad.net/openstack-manuals/+spec/installation-guide-improvements
for tracking.

As little change as possible. Update to MariaDB as you can. Add flat
network if possible.

Thanks Matt for doing this!
Anne


>
> [1]
> https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/juno-staging
>
> Matt
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/432c939e/attachment.html>

From nchase at mirantis.com  Thu Sep 11 17:06:51 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Thu, 11 Sep 2014 13:06:51 -0400
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <54114BF8.7070400@suse.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
 <5410E323.7010507@mirantis.com> <54114BF8.7070400@suse.com>
Message-ID: <5411D6AB.5000609@mirantis.com>


On 9/11/2014 3:15 AM, Andreas Jaeger wrote:
> If you need something to keep track, we can also use an etherpad or 
> wiki page. I consider a separate bug for each issue a lot of overhead, 
> Andreas 

I forget sometimes that we said you can do patches without an associated 
bug. :)

-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
<http://openstacksv.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/a65b8347/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/a65b8347/attachment.png>

From berendt at b1-systems.de  Thu Sep 11 17:46:39 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Thu, 11 Sep 2014 19:46:39 +0200
Subject: [Openstack-docs] Is comment about active/active RabbitMQ config
 still a valid concern?
In-Reply-To: <54108DB4.1030005@windriver.com>
References: <54108DB4.1030005@windriver.com>
Message-ID: <5411DFFF.3070206@b1-systems.de>

On 09/10/2014 07:43 PM, Chris Friesen wrote:
> Is the comment about active/standby being preferred still current or is 
> it stale?

Like in your mail on openstack-dev@ you should mention that the RabbitMQ
developer reommend to use active/active with mirrored queues.

I think we should change this in the HA guide.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From mkassawara at gmail.com  Thu Sep 11 18:08:31 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Thu, 11 Sep 2014 13:08:31 -0500
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <5411D6AB.5000609@mirantis.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
 <5410E323.7010507@mirantis.com> <54114BF8.7070400@suse.com>
 <5411D6AB.5000609@mirantis.com>
Message-ID: <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>

I generally lean toward blueprints to manage a group of similar patches
that involve content updates rather than bugs.

On Thu, Sep 11, 2014 at 12:06 PM, Nicholas Chase <nchase at mirantis.com>
wrote:

>
> On 9/11/2014 3:15 AM, Andreas Jaeger wrote:
>
> If you need something to keep track, we can also use an etherpad or wiki
> page. I consider a separate bug for each issue a lot of overhead, Andreas
>
>
> I forget sometimes that we said you can do patches without an associated
> bug. :)
>
> --
> Nick Chase
> 1-650-567-5640
> Technical Marketing Manager, Mirantis
> Editor, OpenStack:Now
>  <http://openstacksv.com>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/dcc9039c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/dcc9039c/attachment-0001.png>

From nchase at mirantis.com  Thu Sep 11 18:20:56 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Thu, 11 Sep 2014 14:20:56 -0400
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>	<5410E323.7010507@mirantis.com>	<54114BF8.7070400@suse.com>	<5411D6AB.5000609@mirantis.com>
 <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>
Message-ID: <5411E808.4040603@mirantis.com>


Sounds good to me.

On 9/11/2014 2:08 PM, Matt Kassawara wrote:
> I generally lean toward blueprints to manage a group of similar 
> patches that involve content updates rather than bugs.
>
> On Thu, Sep 11, 2014 at 12:06 PM, Nicholas Chase <nchase at mirantis.com 
> <mailto:nchase at mirantis.com>> wrote:
>
>
>     On 9/11/2014 3:15 AM, Andreas Jaeger wrote:
>>     If you need something to keep track, we can also use an etherpad
>>     or wiki page. I consider a separate bug for each issue a lot of
>>     overhead, Andreas 
>
>     I forget sometimes that we said you can do patches without an
>     associated bug. :)
>
>     -- 
>     Nick Chase
>     1-650-567-5640 <tel:1-650-567-5640>
>     Technical Marketing Manager, Mirantis
>     Editor, OpenStack:Now
>     <http://openstacksv.com>
>
>     _______________________________________________
>     Openstack-docs mailing list
>     Openstack-docs at lists.openstack.org
>     <mailto:Openstack-docs at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>

-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
<http://openstacksv.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/ef258ba3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/ef258ba3/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/ef258ba3/attachment-0001.png>

From berendt at b1-systems.de  Thu Sep 11 18:23:25 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Thu, 11 Sep 2014 20:23:25 +0200
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <5411E808.4040603@mirantis.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>	<5410E323.7010507@mirantis.com>	<54114BF8.7070400@suse.com>	<5411D6AB.5000609@mirantis.com>
 <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>
 <5411E808.4040603@mirantis.com>
Message-ID: <5411E89D.4060705@b1-systems.de>

On 09/11/2014 08:20 PM, Nicholas Chase wrote:
> Sounds good to me.

+1

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From aj at suse.com  Thu Sep 11 18:29:51 2014
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 11 Sep 2014 20:29:51 +0200
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <5411E89D.4060705@b1-systems.de>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>	<5410E323.7010507@mirantis.com>	<54114BF8.7070400@suse.com>	<5411D6AB.5000609@mirantis.com>
 <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>
 <5411E808.4040603@mirantis.com> <5411E89D.4060705@b1-systems.de>
Message-ID: <5411EA1F.7090705@suse.com>

On 09/11/2014 08:23 PM, Christian Berendt wrote:
> On 09/11/2014 08:20 PM, Nicholas Chase wrote:
>> Sounds good to me.
> 
> +1

works for me. Please follow the new workflow and create in launchpad and
add the detailed spec in docs-specs.
Who will do this?

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From mkassawara at gmail.com  Thu Sep 11 18:32:17 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Thu, 11 Sep 2014 13:32:17 -0500
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <5411EA1F.7090705@suse.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
 <5410E323.7010507@mirantis.com> <54114BF8.7070400@suse.com>
 <5411D6AB.5000609@mirantis.com>
 <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>
 <5411E808.4040603@mirantis.com> <5411E89D.4060705@b1-systems.de>
 <5411EA1F.7090705@suse.com>
Message-ID: <CABA+jQqHrX5_rDzFy53EijyLaMO2DAvBHb66Qgr4r8JwHNUozw@mail.gmail.com>

I should attempt the docs-specs procedure... haven't built one yet.

On Thu, Sep 11, 2014 at 1:29 PM, Andreas Jaeger <aj at suse.com> wrote:

> On 09/11/2014 08:23 PM, Christian Berendt wrote:
> > On 09/11/2014 08:20 PM, Nicholas Chase wrote:
> >> Sounds good to me.
> >
> > +1
>
> works for me. Please follow the new workflow and create in launchpad and
> add the detailed spec in docs-specs.
> Who will do this?
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/0ffbd9f6/attachment.html>

From anne at openstack.org  Thu Sep 11 18:36:34 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 11 Sep 2014 13:36:34 -0500
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <5411EA1F.7090705@suse.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
 <5410E323.7010507@mirantis.com> <54114BF8.7070400@suse.com>
 <5411D6AB.5000609@mirantis.com>
 <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>
 <5411E808.4040603@mirantis.com> <5411E89D.4060705@b1-systems.de>
 <5411EA1F.7090705@suse.com>
Message-ID: <CAD0KtVGNqME56kW3c7VpyEQQUCpe87qrUy2C6K+NDz_uNnuVKA@mail.gmail.com>

On Thu, Sep 11, 2014 at 1:29 PM, Andreas Jaeger <aj at suse.com> wrote:

> On 09/11/2014 08:23 PM, Christian Berendt wrote:
> > On 09/11/2014 08:20 PM, Nicholas Chase wrote:
> >> Sounds good to me.
> >
> > +1
>
> works for me. Please follow the new workflow and create in launchpad and
> add the detailed spec in docs-specs.
> Who will do this?
>

I had exempted the install guide work from a spec originally -- at least I
thought I did, can't find that on the mailing list.

There's this wiki page:
https://wiki.openstack.org/wiki/Documentation/InstallGuideChanges

which seems sufficient... again balancing between "just write it already"
and the need for consensus on what we're working on first.

In other words, I don't want Matt writing a spec when he could be writing
docs. The decisions don't seem super contentious. Does that make sense?
Anne


>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/7a7f72c8/attachment.html>

From aj at suse.com  Thu Sep 11 18:39:39 2014
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 11 Sep 2014 20:39:39 +0200
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <CAD0KtVGNqME56kW3c7VpyEQQUCpe87qrUy2C6K+NDz_uNnuVKA@mail.gmail.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
 <5410E323.7010507@mirantis.com> <54114BF8.7070400@suse.com>
 <5411D6AB.5000609@mirantis.com>
 <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>
 <5411E808.4040603@mirantis.com> <5411E89D.4060705@b1-systems.de>
 <5411EA1F.7090705@suse.com>
 <CAD0KtVGNqME56kW3c7VpyEQQUCpe87qrUy2C6K+NDz_uNnuVKA@mail.gmail.com>
Message-ID: <5411EC6B.8040504@suse.com>

On 09/11/2014 08:36 PM, Anne Gentle wrote:
> 
> 
> On Thu, Sep 11, 2014 at 1:29 PM, Andreas Jaeger <aj at suse.com
> <mailto:aj at suse.com>> wrote:
> 
>     On 09/11/2014 08:23 PM, Christian Berendt wrote:
>     > On 09/11/2014 08:20 PM, Nicholas Chase wrote:
>     >> Sounds good to me.
>     >
>     > +1
> 
>     works for me. Please follow the new workflow and create in launchpad and
>     add the detailed spec in docs-specs.
>     Who will do this?
> 
> 
> I had exempted the install guide work from a spec originally -- at least
> I thought I did, can't find that on the mailing list. 
> 
> There's this wiki
> page: https://wiki.openstack.org/wiki/Documentation/InstallGuideChanges
> 
> which seems sufficient... again balancing between "just write it
> already" and the need for consensus on what we're working on first.
> 
> In other words, I don't want Matt writing a spec when he could be
> writing docs. The decisions don't seem super contentious. Does that make
> sense?

I'm fine doing it without a spec - but if you do it, do it properly.

I'm also fine doing it without a bug ;)

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Thu Sep 11 18:44:11 2014
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 11 Sep 2014 20:44:11 +0200
Subject: [Openstack-docs] Installation guide updates for Juno
In-Reply-To: <5411EC6B.8040504@suse.com>
References: <CABA+jQq0SuWaVLBp0ZGgxk8EPB2FH8v7+8ygMv6yqtwQSfSKfQ@mail.gmail.com>
 <5410E323.7010507@mirantis.com> <54114BF8.7070400@suse.com>
 <5411D6AB.5000609@mirantis.com>
 <CABA+jQrV14_07H4f9f4igS4qmBQdH0UkQAtcKJTBb6Ld56U0iw@mail.gmail.com>
 <5411E808.4040603@mirantis.com> <5411E89D.4060705@b1-systems.de>
 <5411EA1F.7090705@suse.com>
 <CAD0KtVGNqME56kW3c7VpyEQQUCpe87qrUy2C6K+NDz_uNnuVKA@mail.gmail.com>
 <5411EC6B.8040504@suse.com>
Message-ID: <5411ED7B.8050904@suse.com>

On 09/11/2014 08:39 PM, Andreas Jaeger wrote:
> On 09/11/2014 08:36 PM, Anne Gentle wrote:
>>
>>
>> On Thu, Sep 11, 2014 at 1:29 PM, Andreas Jaeger <aj at suse.com
>> <mailto:aj at suse.com>> wrote:
>>
>>     On 09/11/2014 08:23 PM, Christian Berendt wrote:
>>     > On 09/11/2014 08:20 PM, Nicholas Chase wrote:
>>     >> Sounds good to me.
>>     >
>>     > +1
>>
>>     works for me. Please follow the new workflow and create in launchpad and
>>     add the detailed spec in docs-specs.
>>     Who will do this?
>>
>>
>> I had exempted the install guide work from a spec originally -- at least
>> I thought I did, can't find that on the mailing list. 
>>
>> There's this wiki
>> page: https://wiki.openstack.org/wiki/Documentation/InstallGuideChanges
>>
>> which seems sufficient... again balancing between "just write it
>> already" and the need for consensus on what we're working on first.
>>
>> In other words, I don't want Matt writing a spec when he could be
>> writing docs. The decisions don't seem super contentious. Does that make
>> sense?
> 
> I'm fine doing it without a spec - but if you do it, do it properly.
> 
> I'm also fine doing it without a bug ;)

Just learned that there's an existing blueprint, ok let's reuse that and
not use docs-specs this time. We can do it properly next cycle,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From anne at openstack.org  Fri Sep 12 15:48:07 2014
From: anne at openstack.org (Anne Gentle)
Date: Fri, 12 Sep 2014 10:48:07 -0500
Subject: [Openstack-docs] Network troubleshooting
Message-ID: <CAD0KtVFh06pUFogg3o3wL-0G_Ag8gs17rR8Nv-vsZ4WnKMvsZQ@mail.gmail.com>

Hi all, especially those interested in the separate Networking Guide:

I attempted to bring in network troubleshooting wholesale from the Ops
Guide with https://review.openstack.org/#/c/113066. However it's a bit
over-reaching since it shows how to troubleshoot nova-network. So yesterday
on IRC a few of us said we could pull these four topics in:
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#neutron_network_traffic_in_cloud
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#trouble_shooting_ovs
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#dealing_with_netns

http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#failure_in_path

My question/request is this: Phil, what do you already have written about
neutron troubleshooting that we can reuse in this doc? What other parts
could I pull in from the Ops Guide? Should the neutron-debug command be
brought into this guide?

I'm going to give the patch another go, so wanted to bring it to the group
(and list's) attention.
Thanks,
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/208e87a3/attachment.html>

From aj at suse.com  Fri Sep 12 16:54:29 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 12 Sep 2014 18:54:29 +0200
Subject: [Openstack-docs] Unifiying option for Block Storage
Message-ID: <54132545.1080005@suse.com>

Reviewing some patches I noticed that different drivers use different
wording for the "Supported operations" section and I'd like to unify them.

I see two options for the list:
1)
    Create volume
    Delete volume
    Attach volume
    Detach volume
    Clone volume
    Extend volume
    Create snapshot
    Delete snapshot
    Copy image to volume
    Copy volume to image
    Create volume from snapshot
    Get statistics
    Migrate volume with back-end assistance
    Retype volume
2)
    Create and delete volume
    Attach and detach volume
    Clone volume
    Extend volume
    Create and delete snapshot
    Copy image to volume
    Copy volume to image
    Create volume from snapshot
    Get statistics
    Migrate volume with back-end assistance
    Retype volume

Any preferences or different suggestions?

Reference:
http://docs.openstack.org/trunk/config-reference/content/section_volume-drivers.html

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From phil.hopkins at rackspace.com  Fri Sep 12 19:36:58 2014
From: phil.hopkins at rackspace.com (Phil Hopkins)
Date: Fri, 12 Sep 2014 19:36:58 +0000
Subject: [Openstack-docs] Network troubleshooting
In-Reply-To: <CAD0KtVFh06pUFogg3o3wL-0G_Ag8gs17rR8Nv-vsZ4WnKMvsZQ@mail.gmail.com>
References: <CAD0KtVFh06pUFogg3o3wL-0G_Ag8gs17rR8Nv-vsZ4WnKMvsZQ@mail.gmail.com>
Message-ID: <FBC99830465C784CAF93C211A517C0F493E25914@ORD1EXD03.RACKSPACE.CORP>

I have several slides that I use in my training but I haven't written anything. The whole network troubleshooting section from the OPS guide is a good start but it is mostly focused on nova-networks with a little neutron thrown in around the edges.

I will be out on vacation next week but the following week I will take a close look and give a stab at writing some neutron to flesh it out.

[X][X][X][X]
Phil Hopkins RHCA CMDBA
Openstack Instructor
Rackspace Hostingtm
(210) 312-3584
________________________________
From: annegentle at justwriteclick.com [annegentle at justwriteclick.com] on behalf of Anne Gentle [anne at openstack.org]
Sent: Friday, September 12, 2014 10:48 AM
To: Matt Kassawara; Phil Hopkins; edgar.magana at workday.com; openstack-docs at lists.openstack.org; Nick Chase
Subject: Network troubleshooting

Hi all, especially those interested in the separate Networking Guide:

I attempted to bring in network troubleshooting wholesale from the Ops Guide with https://review.openstack.org/#/c/113066. However it's a bit over-reaching since it shows how to troubleshoot nova-network. So yesterday on IRC a few of us said we could pull these four topics in:
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#neutron_network_traffic_in_cloud
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#trouble_shooting_ovs
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#dealing_with_netns
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#failure_in_path

My question/request is this: Phil, what do you already have written about neutron troubleshooting that we can reuse in this doc? What other parts could I pull in from the Ops Guide? Should the neutron-debug command be brought into this guide?

I'm going to give the patch another go, so wanted to bring it to the group (and list's) attention.
Thanks,
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/e374249b/attachment.html>

From matt.kassawara at RACKSPACE.COM  Fri Sep 12 19:41:09 2014
From: matt.kassawara at RACKSPACE.COM (Matt Kassawara)
Date: Fri, 12 Sep 2014 19:41:09 +0000
Subject: [Openstack-docs] Network troubleshooting
In-Reply-To: <FBC99830465C784CAF93C211A517C0F493E25914@ORD1EXD03.RACKSPACE.CORP>
References: <CAD0KtVFh06pUFogg3o3wL-0G_Ag8gs17rR8Nv-vsZ4WnKMvsZQ@mail.gmail.com>
 <FBC99830465C784CAF93C211A517C0F493E25914@ORD1EXD03.RACKSPACE.CORP>
Message-ID: <D038B669.1AF2%matt.kassawara@rackspace.com>

Slides might be useful? especially if they cover various neutron components and scenarios.

From: Phil Hopkins <phil.hopkins at rackspace.com<mailto:phil.hopkins at rackspace.com>>
Date: Friday, September 12, 2014 at 2:36 PM
To: Anne Gentle <anne at openstack.org<mailto:anne at openstack.org>>, Matthew Kassawara <matt.kassawara at rackspace.com<mailto:matt.kassawara at rackspace.com>>, "edgar.magana at workday.com<mailto:edgar.magana at workday.com>" <edgar.magana at workday.com<mailto:edgar.magana at workday.com>>, "openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>" <openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>>, Nick Chase <nchase at mirantis.com<mailto:nchase at mirantis.com>>
Subject: RE: Network troubleshooting

I have several slides that I use in my training but I haven't written anything. The whole network troubleshooting section from the OPS guide is a good start but it is mostly focused on nova-networks with a little neutron thrown in around the edges.

I will be out on vacation next week but the following week I will take a close look and give a stab at writing some neutron to flesh it out.

[X][X][X][X]
Phil Hopkins RHCA CMDBA
Openstack Instructor
Rackspace Hostingtm
(210) 312-3584
________________________________
From: annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com> [annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com>] on behalf of Anne Gentle [anne at openstack.org<mailto:anne at openstack.org>]
Sent: Friday, September 12, 2014 10:48 AM
To: Matt Kassawara; Phil Hopkins; edgar.magana at workday.com<mailto:edgar.magana at workday.com>; openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>; Nick Chase
Subject: Network troubleshooting

Hi all, especially those interested in the separate Networking Guide:

I attempted to bring in network troubleshooting wholesale from the Ops Guide with https://review.openstack.org/#/c/113066. However it's a bit over-reaching since it shows how to troubleshoot nova-network. So yesterday on IRC a few of us said we could pull these four topics in:
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#neutron_network_traffic_in_cloud
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#trouble_shooting_ovs
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#dealing_with_netns
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#failure_in_path

My question/request is this: Phil, what do you already have written about neutron troubleshooting that we can reuse in this doc? What other parts could I pull in from the Ops Guide? Should the neutron-debug command be brought into this guide?

I'm going to give the patch another go, so wanted to bring it to the group (and list's) attention.
Thanks,
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/fac59ce3/attachment-0001.html>

From phil.hopkins at rackspace.com  Fri Sep 12 19:48:44 2014
From: phil.hopkins at rackspace.com (Phil Hopkins)
Date: Fri, 12 Sep 2014 19:48:44 +0000
Subject: [Openstack-docs] Network troubleshooting
In-Reply-To: <D038B669.1AF2%matt.kassawara@rackspace.com>
References: <CAD0KtVFh06pUFogg3o3wL-0G_Ag8gs17rR8Nv-vsZ4WnKMvsZQ@mail.gmail.com>
 <FBC99830465C784CAF93C211A517C0F493E25914@ORD1EXD03.RACKSPACE.CORP>,
 <D038B669.1AF2%matt.kassawara@rackspace.com>
Message-ID: <FBC99830465C784CAF93C211A517C0F493E25950@ORD1EXD03.RACKSPACE.CORP>

They are very basic and I don't think they add much value. I have attached them.  Again I will work on writing some additional material starting the week of Sept. 22. It shouldn't take too long to get some text together.

[X][X][X][X]
Phil Hopkins RHCA CMDBA
Openstack Instructor
Rackspace Hostingtm
(210) 312-3584
________________________________
From: Matt Kassawara
Sent: Friday, September 12, 2014 2:41 PM
To: Phil Hopkins; Anne Gentle; edgar.magana at workday.com; openstack-docs at lists.openstack.org; Nick Chase
Subject: Re: Network troubleshooting

Slides might be useful? especially if they cover various neutron components and scenarios.

From: Phil Hopkins <phil.hopkins at rackspace.com<mailto:phil.hopkins at rackspace.com>>
Date: Friday, September 12, 2014 at 2:36 PM
To: Anne Gentle <anne at openstack.org<mailto:anne at openstack.org>>, Matthew Kassawara <matt.kassawara at rackspace.com<mailto:matt.kassawara at rackspace.com>>, "edgar.magana at workday.com<mailto:edgar.magana at workday.com>" <edgar.magana at workday.com<mailto:edgar.magana at workday.com>>, "openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>" <openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>>, Nick Chase <nchase at mirantis.com<mailto:nchase at mirantis.com>>
Subject: RE: Network troubleshooting

I have several slides that I use in my training but I haven't written anything. The whole network troubleshooting section from the OPS guide is a good start but it is mostly focused on nova-networks with a little neutron thrown in around the edges.

I will be out on vacation next week but the following week I will take a close look and give a stab at writing some neutron to flesh it out.

[X][X][X][X]
Phil Hopkins RHCA CMDBA
Openstack Instructor
Rackspace Hostingtm
(210) 312-3584
________________________________
From: annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com> [annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com>] on behalf of Anne Gentle [anne at openstack.org<mailto:anne at openstack.org>]
Sent: Friday, September 12, 2014 10:48 AM
To: Matt Kassawara; Phil Hopkins; edgar.magana at workday.com<mailto:edgar.magana at workday.com>; openstack-docs at lists.openstack.org<mailto:openstack-docs at lists.openstack.org>; Nick Chase
Subject: Network troubleshooting

Hi all, especially those interested in the separate Networking Guide:

I attempted to bring in network troubleshooting wholesale from the Ops Guide with https://review.openstack.org/#/c/113066. However it's a bit over-reaching since it shows how to troubleshoot nova-network. So yesterday on IRC a few of us said we could pull these four topics in:
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#neutron_network_traffic_in_cloud
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#trouble_shooting_ovs
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#dealing_with_netns
http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#failure_in_path

My question/request is this: Phil, what do you already have written about neutron troubleshooting that we can reuse in this doc? What other parts could I pull in from the Ops Guide? Should the neutron-debug command be brought into this guide?

I'm going to give the patch another go, so wanted to bring it to the group (and list's) attention.
Thanks,
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/df2f829d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: neutrontroubleshoot.pdf
Type: application/pdf
Size: 197284 bytes
Desc: neutrontroubleshoot.pdf
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/df2f829d/attachment-0001.pdf>

From nchase at mirantis.com  Fri Sep 12 20:16:46 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Fri, 12 Sep 2014 16:16:46 -0400
Subject: [Openstack-docs] Install Guide Status
Message-ID: <541354AE.8050108@mirantis.com>


    Now that packages have started to drop it's Install Guide season, so
    I've been talking to Matt about what needs to be done, and here's
    where we are:

    Structurally, we've all sort of decided that we're not going to make
    any unnecessary changes, so there's not a huge amount of work to
    do.  Also, based on the Ubuntu packages, it appears that aside from
    determining which of the handful of workarounds we had to add for
    Icehouse are still necessary for Juno, hopefully we won't have a ton
    to do.  Most of the changes so far involve configuration files...
    just a handful of distro/packaging workarounds so far and no doubt
    those will change prior to release. He's also trying to replace
    MySQL with MariaDB, except for SLES, and remove support for RHEL 6.x
    and Ubuntu 12.04. Other changes may include minor adjustments to
    nova-network -- "(it won't go away!)" -- to make it mirror neutron
    more closely with the concept of internal (tenant) and external
    (floating IP) networks.


    Note that this is based on the Ubuntu packages, which are themselves
    based on Milestone 2, and NOT Milestone 3, so that could of course
    change when we get the final, and when we start digging into other
    distros.

    When we get this done, Matt estimates that we should be about 85%
    towards completion of the "Improve the Install Guide" project; there
    are still some sections that need rewriting for quality, but not
    necessarily for content. (In other words, they work, but they can be
    better written.)  The last big chunk of the install guide
    improvements project involves Swift, and he feels that the ability
    to tag someone familiar with it would help move patches. He's also a
    bit concerned about trove, and I'm going to work with him to find
    out what's needed there and track sown some resources. The remaining
    improvements include networking (which served as a baseline for many
    of the improvements) and a consistency validation for the entire
    guide (after some subjective review issues).

-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
<http://openstacksv.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/a12a66bd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/a12a66bd/attachment.png>

From mkassawara at gmail.com  Fri Sep 12 22:31:41 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Fri, 12 Sep 2014 17:31:41 -0500
Subject: [Openstack-docs] Install Guide Status
In-Reply-To: <541354AE.8050108@mirantis.com>
References: <541354AE.8050108@mirantis.com>
Message-ID: <CABA+jQqbVoY3ky3NyUwGt3CyEsVLFWmmGcu1HR-Yq7wgdyjUzA@mail.gmail.com>

I created a wiki page covering necessary changes (so far) for Juno based on
a combination of the following:

1) Configuration file changes from the configuration reference.
2) Installation of "core" services on Ubuntu using Juno milestone 2
packages. Both the neutron and nova-network environments appear to work.
However, the milestone 2 packages don't fully support the [neutron] section
in nova.conf so the neutron environment uses a mixture of old and new
locations.

Surprisingly, I didn't have to peek at gate configurations for hints. Also,
I'm still waiting on packages for RH/CentOS/Fedora and hope someone
familiar with SUSE and Debian can validate these changes well ahead of
release on 16 October.

https://wiki.openstack.org/wiki/Documentation/InstallationGuideJuno

On Fri, Sep 12, 2014 at 3:16 PM, Nicholas Chase <nchase at mirantis.com> wrote:

>
> Now that packages have started to drop it's Install Guide season, so I've
> been talking to Matt about what needs to be done, and here's where we are:
>
> Structurally, we've all sort of decided that we're not going to make any
> unnecessary changes, so there's not a huge amount of work to do.  Also,
> based on the Ubuntu packages, it appears that aside from determining which
> of the handful of workarounds we had to add for Icehouse are still
> necessary for Juno, hopefully we won't have a ton to do.  Most of the
> changes so far involve configuration files? just a handful of
> distro/packaging workarounds so far and no doubt those will change prior to
> release. He's also trying to replace MySQL with MariaDB, except for SLES,
> and remove support for RHEL 6.x and Ubuntu 12.04. Other changes may include
> minor adjustments to nova-network -- "(it won?t go away!)" -- to make it
> mirror neutron more closely with the concept of internal (tenant) and
> external (floating IP) networks.
>
>
>   Note that this is based on the Ubuntu packages, which are themselves
> based on Milestone 2, and NOT Milestone 3, so that could of course change
> when we get the final, and when we start digging into other distros.
>
> When we get this done, Matt estimates that we should be about 85% towards
> completion of the "Improve the Install Guide" project; there are still some
> sections that need rewriting for quality, but not necessarily for content.
> (In other words, they work, but they can be better written.)  The last big
> chunk of the install guide improvements project involves Swift, and he
> feels that the ability to tag someone familiar with it would help move
> patches. He's also a bit concerned about trove, and I'm going to work with
> him to find out what's needed there and track sown some resources. The
> remaining improvements include networking (which served as a baseline for
> many of the improvements) and a consistency validation for the entire guide
> (after some subjective review issues).
>
>   --
> Nick Chase
> 1-650-567-5640
> Technical Marketing Manager, Mirantis
> Editor, OpenStack:Now
>  <http://openstacksv.com>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/f6b0e7c8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140912/f6b0e7c8/attachment-0001.png>

From sgordon at redhat.com  Sat Sep 13 03:20:01 2014
From: sgordon at redhat.com (Steve Gordon)
Date: Fri, 12 Sep 2014 23:20:01 -0400 (EDT)
Subject: [Openstack-docs] Install Guide Status
In-Reply-To: <CABA+jQqbVoY3ky3NyUwGt3CyEsVLFWmmGcu1HR-Yq7wgdyjUzA@mail.gmail.com>
References: <541354AE.8050108@mirantis.com>
 <CABA+jQqbVoY3ky3NyUwGt3CyEsVLFWmmGcu1HR-Yq7wgdyjUzA@mail.gmail.com>
Message-ID: <1537181330.13478379.1410578401358.JavaMail.zimbra@redhat.com>

----- Original Message -----
> From: "Matt Kassawara" <mkassawara at gmail.com>
> To: "Nicholas Chase" <nchase at mirantis.com>
> 
> I created a wiki page covering necessary changes (so far) for Juno based on
> a combination of the following:
> 
> 1) Configuration file changes from the configuration reference.
> 2) Installation of "core" services on Ubuntu using Juno milestone 2
> packages. Both the neutron and nova-network environments appear to work.
> However, the milestone 2 packages don't fully support the [neutron] section
> in nova.conf so the neutron environment uses a mixture of old and new
> locations.
> 
> Surprisingly, I didn't have to peek at gate configurations for hints. Also,
> I'm still waiting on packages for RH/CentOS/Fedora and hope someone
> familiar with SUSE and Debian can validate these changes well ahead of
> release on 16 October.

We're currently running CI on M-3 based packages for RDO. Unfortunately there has still been a heavy skew towards feature delivery in the last milestone in Juno (e.g. M-1: 4 blueprints, M-2: 8 blueprints, M-3 26: blueprints in Nova) so I would expect there is quite some potential for change there.

-Steve


From aj at suse.com  Sat Sep 13 17:33:08 2014
From: aj at suse.com (Andreas Jaeger)
Date: Sat, 13 Sep 2014 19:33:08 +0200
Subject: [Openstack-docs] Redirects for /trunk/install-guide?
In-Reply-To: <f22b5bd2c8fbcd5e69c3ac9d4749bf75@objectif-libre.com>
References: <54047861.8020404@suse.com>
 <f22b5bd2c8fbcd5e69c3ac9d4749bf75@objectif-libre.com>
Message-ID: <54147FD4.7090400@suse.com>

On 09/08/2014 06:59 AM, Gauvain Pocentek wrote:
> Le 2014-09-01 15:45, Andreas Jaeger a ?crit :
>> I suggest to not do any redirects for /trunk/install-guide - this is the
>> draft version and we should not do redirects for any change there.
>>
>> https://review.openstack.org/#/c/118130
>>
>> Does this work for you?
> 
> Works for me!
> 
> Did we reach an agreement on this? I'd like to make sure that everyone's
> OK with this decision before approving Joseph's ID changes patch
> (https://review.openstack.org/#/c/118097/).

Nope raised any concerns, so let's move forward with it...

I've send a patch to remove the one occurence we had already:

https://review.openstack.org/121361

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Sat Sep 13 17:55:39 2014
From: aj at suse.com (Andreas Jaeger)
Date: Sat, 13 Sep 2014 19:55:39 +0200
Subject: [Openstack-docs] Unifiying option for Block Storage
In-Reply-To: <54132545.1080005@suse.com>
References: <54132545.1080005@suse.com>
Message-ID: <5414851B.1020301@suse.com>

On 09/12/2014 06:54 PM, Andreas Jaeger wrote:
> Reviewing some patches I noticed that different drivers use different
> wording for the "Supported operations" section and I'd like to unify them.
> 
> I see two options for the list:
> 1)
>     Create volume
>     Delete volume
>     Attach volume
>     Detach volume
>     Clone volume
>     Extend volume
>     Create snapshot
>     Delete snapshot
>     Copy image to volume
>     Copy volume to image
>     Create volume from snapshot
>     Get statistics
>     Migrate volume with back-end assistance
>     Retype volume
> 2)
>     Create and delete volume
>     Attach and detach volume
>     Clone volume
>     Extend volume
>     Create and delete snapshot
>     Copy image to volume
>     Copy volume to image
>     Create volume from snapshot
>     Get statistics
>     Migrate volume with back-end assistance
>     Retype volume
> 
> Any preferences or different suggestions?

Looking a bit deeper, I decided to go with this list:

Create, delete, attach, and detach volumes.
Create, list, and delete volume snapshots.
Create a volume from a snapshot.
Copy an image to a volume.
Copy a volume to an image.
Clone a volume.
Extend a volume.
Get volume statistics.
...

A first patch is here:
https://review.openstack.org/121366

Please tell me whether I should continue this way, I've marked the
patch as WIP for now to get your input,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From anne at openstack.org  Sun Sep 14 18:16:33 2014
From: anne at openstack.org (Anne Gentle)
Date: Sun, 14 Sep 2014 13:16:33 -0500
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
	team
In-Reply-To: <D0332543.83DD%edgar.magana@workday.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
 <D0332543.83DD%edgar.magana@workday.com>
Message-ID: <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>

On Mon, Sep 8, 2014 at 11:20 AM, Edgar Magana <edgar.magana at workday.com>
wrote:

>  Can you guys include me in any further discussions?
> I want to help..
>
>  Thanks,
>
>  Edgar
>
>   From: Adam Lawson <alawson at aqorn.com>
> Date: Tuesday, August 26, 2014 at 11:48 AM
> To: Anne Gentle <anne at openstack.org>
> Cc: David Medberry <david.medberry at canonical.com>, Sriram Subramanian <
> sriram at sriramhere.com>, "openstack-docs at lists.openstack.org" <
> openstack-docs at lists.openstack.org>, "
> openstack-operators at lists.openstack.org" <
> openstack-operators at lists.openstack.org>
> Subject: Re: [Openstack-operators] High Availability Guide team
>
>   I'd be happy to participate as needed Anne.
> On Aug 26, 2014 11:10 AM, "Anne Gentle" <anne at openstack.org> wrote:
>
>> Hi all,
>> Cross-posting to -docs and -operators.
>>
>>  At the Ops mid-cycle meetup this week, Matt Griffin, David Medberry,
>> and Sriram Subramanian offered to start a review team for the High
>> Availability Guide. It needs some updates and it's best if the review team
>> works similar to the Security Guide -- subject matter experts working with
>> core docs team members for reviews. So I'm proposing we pull it into its
>> own repo just like the Security Guide. Any reasons not to? I think the next
>> steps are:
>>
>>  1. Propose a patch to openstack/governance to show the repo is governed
>> by the Docs program.
>> 2. Propose a patch that sets up a separate review team starting with
>> Matt, David, and Sriram. We think Emilien would be interested too, sound
>> good? Any others? We can have members of openstack-docs-core as well,
>> similar to the Security Guide.
>> 3. Propose a patch that gets that guide building separately in a
>> different repo.
>> 4.  Start working on the four bugs already logged [1] and logged more as
>> needed.
>>
>>
Hi all,
Sounds like we still need the tasks above to happen.

Sriram and Andreas, I've got a branch with the HA Guide separated out at
https://github.com/annegentle/ha-guide -- can you take a look and see if we
can use it for the starting point? If it's good-to-go, I can take tasks 1
and 3. (Sriram, I hope you didn't get too far with the separate repo,
holler if you want to divvy up either of those.)

Thanks all for the interest! Feel free to start with a weekly meeting if
that makes sense. I know David, Matt, and Sriram are willing to help out
and a lot of you raised your hands on this thread as well. Nearly there!
Thanks,
Anne


>  Any other subtasks? Any interested parties?
>>
>>  Thanks,
>> Anne
>>
>>  1.
>> https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140914/64173229/attachment.html>

From aj at suse.com  Sun Sep 14 19:25:41 2014
From: aj at suse.com (Andreas Jaeger)
Date: Sun, 14 Sep 2014 21:25:41 +0200
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
 team
In-Reply-To: <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
 <D0332543.83DD%edgar.magana@workday.com>
 <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>
Message-ID: <5415EBB5.1000806@suse.com>

On 09/14/2014 08:16 PM, Anne Gentle wrote:
> 
> 
> On Mon, Sep 8, 2014 at 11:20 AM, Edgar Magana <edgar.magana at workday.com
> <mailto:edgar.magana at workday.com>> wrote:
> 
>     Can you guys include me in any further discussions?
>     I want to help..
> 
>     Thanks,
> 
>     Edgar
> 
>     From: Adam Lawson <alawson at aqorn.com <mailto:alawson at aqorn.com>>
>     Date: Tuesday, August 26, 2014 at 11:48 AM
>     To: Anne Gentle <anne at openstack.org <mailto:anne at openstack.org>>
>     Cc: David Medberry <david.medberry at canonical.com
>     <mailto:david.medberry at canonical.com>>, Sriram Subramanian
>     <sriram at sriramhere.com <mailto:sriram at sriramhere.com>>,
>     "openstack-docs at lists.openstack.org
>     <mailto:openstack-docs at lists.openstack.org>"
>     <openstack-docs at lists.openstack.org
>     <mailto:openstack-docs at lists.openstack.org>>,
>     "openstack-operators at lists.openstack.org
>     <mailto:openstack-operators at lists.openstack.org>"
>     <openstack-operators at lists.openstack.org
>     <mailto:openstack-operators at lists.openstack.org>>
>     Subject: Re: [Openstack-operators] High Availability Guide team
> 
>     I'd be happy to participate as needed Anne.
> 
>     On Aug 26, 2014 11:10 AM, "Anne Gentle" <anne at openstack.org
>     <mailto:anne at openstack.org>> wrote:
> 
>         Hi all, 
>         Cross-posting to -docs and -operators. 
> 
>         At the Ops mid-cycle meetup this week, Matt Griffin, David
>         Medberry, and Sriram Subramanian offered to start a review team
>         for the High Availability Guide. It needs some updates and it's
>         best if the review team works similar to the Security Guide --
>         subject matter experts working with core docs team members for
>         reviews. So I'm proposing we pull it into its own repo just like
>         the Security Guide. Any reasons not to? I think the next steps are:
> 
>         1. Propose a patch to openstack/governance to show the repo is
>         governed by the Docs program.
>         2. Propose a patch that sets up a separate review team starting
>         with Matt, David, and Sriram. We think Emilien would be
>         interested too, sound good? Any others? We can have members of
>         openstack-docs-core as well, similar to the Security Guide.
>         3. Propose a patch that gets that guide building separately in a
>         different repo.
>         4.  Start working on the four bugs already logged [1] and logged
>         more as needed.
> 
> 
> Hi all, 
> Sounds like we still need the tasks above to happen.
> 
> Sriram and Andreas, I've got a branch with the HA Guide separated out
> at https://github.com/annegentle/ha-guide -- can you take a look and see
> if we can use it for the starting point? If it's good-to-go, I can take
> tasks 1 and 3. (Sriram, I hope you didn't get too far with the separate
> repo, holler if you want to divvy up either of those.)

That is as simple import without all the history and seems to have one
level too much.

I propose to do use git filter-branch to keep the history intact,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Sun Sep 14 20:19:21 2014
From: aj at suse.com (Andreas Jaeger)
Date: Sun, 14 Sep 2014 22:19:21 +0200
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
 team
In-Reply-To: <5415EBB5.1000806@suse.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
 <D0332543.83DD%edgar.magana@workday.com>
 <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>
 <5415EBB5.1000806@suse.com>
Message-ID: <5415F849.9030405@suse.com>

On 09/14/2014 09:25 PM, Andreas Jaeger wrote:
> On 09/14/2014 08:16 PM, Anne Gentle wrote:
>>
>>
>> On Mon, Sep 8, 2014 at 11:20 AM, Edgar Magana <edgar.magana at workday.com
>> <mailto:edgar.magana at workday.com>> wrote:
>>
>>     Can you guys include me in any further discussions?
>>     I want to help..
>>
>>     Thanks,
>>
>>     Edgar
>>
>>     From: Adam Lawson <alawson at aqorn.com <mailto:alawson at aqorn.com>>
>>     Date: Tuesday, August 26, 2014 at 11:48 AM
>>     To: Anne Gentle <anne at openstack.org <mailto:anne at openstack.org>>
>>     Cc: David Medberry <david.medberry at canonical.com
>>     <mailto:david.medberry at canonical.com>>, Sriram Subramanian
>>     <sriram at sriramhere.com <mailto:sriram at sriramhere.com>>,
>>     "openstack-docs at lists.openstack.org
>>     <mailto:openstack-docs at lists.openstack.org>"
>>     <openstack-docs at lists.openstack.org
>>     <mailto:openstack-docs at lists.openstack.org>>,
>>     "openstack-operators at lists.openstack.org
>>     <mailto:openstack-operators at lists.openstack.org>"
>>     <openstack-operators at lists.openstack.org
>>     <mailto:openstack-operators at lists.openstack.org>>
>>     Subject: Re: [Openstack-operators] High Availability Guide team
>>
>>     I'd be happy to participate as needed Anne.
>>
>>     On Aug 26, 2014 11:10 AM, "Anne Gentle" <anne at openstack.org
>>     <mailto:anne at openstack.org>> wrote:
>>
>>         Hi all, 
>>         Cross-posting to -docs and -operators. 
>>
>>         At the Ops mid-cycle meetup this week, Matt Griffin, David
>>         Medberry, and Sriram Subramanian offered to start a review team
>>         for the High Availability Guide. It needs some updates and it's
>>         best if the review team works similar to the Security Guide --
>>         subject matter experts working with core docs team members for
>>         reviews. So I'm proposing we pull it into its own repo just like
>>         the Security Guide. Any reasons not to? I think the next steps are:
>>
>>         1. Propose a patch to openstack/governance to show the repo is
>>         governed by the Docs program.
>>         2. Propose a patch that sets up a separate review team starting
>>         with Matt, David, and Sriram. We think Emilien would be
>>         interested too, sound good? Any others? We can have members of
>>         openstack-docs-core as well, similar to the Security Guide.
>>         3. Propose a patch that gets that guide building separately in a
>>         different repo.
>>         4.  Start working on the four bugs already logged [1] and logged
>>         more as needed.
>>
>>
>> Hi all, 
>> Sounds like we still need the tasks above to happen.
>>
>> Sriram and Andreas, I've got a branch with the HA Guide separated out
>> at https://github.com/annegentle/ha-guide -- can you take a look and see
>> if we can use it for the starting point? If it's good-to-go, I can take
>> tasks 1 and 3. (Sriram, I hope you didn't get too far with the separate
>> repo, holler if you want to divvy up either of those.)
> 
> That is as simple import without all the history and seems to have one
> level too much.
> 
> I propose to do use git filter-branch to keep the history intact,

Have a look at:

https://github.com/ajaeger/ha-guide/tree/master/doc

This one misses the top-level files that were in your directory but I
can add them back later on.

Sriram, do you have the perfect solution? ;)

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From anne at openstack.org  Sun Sep 14 23:24:54 2014
From: anne at openstack.org (Anne Gentle)
Date: Sun, 14 Sep 2014 18:24:54 -0500
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
	team
In-Reply-To: <5415F849.9030405@suse.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
 <D0332543.83DD%edgar.magana@workday.com>
 <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>
 <5415EBB5.1000806@suse.com> <5415F849.9030405@suse.com>
Message-ID: <CAD0KtVFSUq_LKnOJLy9_3ubu0KczM7aU1Y9hcMn+H3b=jkaTew@mail.gmail.com>

Cool trick. :) I think I got it all but please do double-check:
https://review.openstack.org/121426

The upstream this will pull from is https://github.com/annegentle/ha-guide

Thanks,

Anne

On Sun, Sep 14, 2014 at 3:19 PM, Andreas Jaeger <aj at suse.com> wrote:

> On 09/14/2014 09:25 PM, Andreas Jaeger wrote:
> > On 09/14/2014 08:16 PM, Anne Gentle wrote:
> >>
> >>
> >> On Mon, Sep 8, 2014 at 11:20 AM, Edgar Magana <edgar.magana at workday.com
> >> <mailto:edgar.magana at workday.com>> wrote:
> >>
> >>     Can you guys include me in any further discussions?
> >>     I want to help..
> >>
> >>     Thanks,
> >>
> >>     Edgar
> >>
> >>     From: Adam Lawson <alawson at aqorn.com <mailto:alawson at aqorn.com>>
> >>     Date: Tuesday, August 26, 2014 at 11:48 AM
> >>     To: Anne Gentle <anne at openstack.org <mailto:anne at openstack.org>>
> >>     Cc: David Medberry <david.medberry at canonical.com
> >>     <mailto:david.medberry at canonical.com>>, Sriram Subramanian
> >>     <sriram at sriramhere.com <mailto:sriram at sriramhere.com>>,
> >>     "openstack-docs at lists.openstack.org
> >>     <mailto:openstack-docs at lists.openstack.org>"
> >>     <openstack-docs at lists.openstack.org
> >>     <mailto:openstack-docs at lists.openstack.org>>,
> >>     "openstack-operators at lists.openstack.org
> >>     <mailto:openstack-operators at lists.openstack.org>"
> >>     <openstack-operators at lists.openstack.org
> >>     <mailto:openstack-operators at lists.openstack.org>>
> >>     Subject: Re: [Openstack-operators] High Availability Guide team
> >>
> >>     I'd be happy to participate as needed Anne.
> >>
> >>     On Aug 26, 2014 11:10 AM, "Anne Gentle" <anne at openstack.org
> >>     <mailto:anne at openstack.org>> wrote:
> >>
> >>         Hi all,
> >>         Cross-posting to -docs and -operators.
> >>
> >>         At the Ops mid-cycle meetup this week, Matt Griffin, David
> >>         Medberry, and Sriram Subramanian offered to start a review team
> >>         for the High Availability Guide. It needs some updates and it's
> >>         best if the review team works similar to the Security Guide --
> >>         subject matter experts working with core docs team members for
> >>         reviews. So I'm proposing we pull it into its own repo just like
> >>         the Security Guide. Any reasons not to? I think the next steps
> are:
> >>
> >>         1. Propose a patch to openstack/governance to show the repo is
> >>         governed by the Docs program.
> >>         2. Propose a patch that sets up a separate review team starting
> >>         with Matt, David, and Sriram. We think Emilien would be
> >>         interested too, sound good? Any others? We can have members of
> >>         openstack-docs-core as well, similar to the Security Guide.
> >>         3. Propose a patch that gets that guide building separately in a
> >>         different repo.
> >>         4.  Start working on the four bugs already logged [1] and logged
> >>         more as needed.
> >>
> >>
> >> Hi all,
> >> Sounds like we still need the tasks above to happen.
> >>
> >> Sriram and Andreas, I've got a branch with the HA Guide separated out
> >> at https://github.com/annegentle/ha-guide -- can you take a look and
> see
> >> if we can use it for the starting point? If it's good-to-go, I can take
> >> tasks 1 and 3. (Sriram, I hope you didn't get too far with the separate
> >> repo, holler if you want to divvy up either of those.)
> >
> > That is as simple import without all the history and seems to have one
> > level too much.
> >
> > I propose to do use git filter-branch to keep the history intact,
>
> Have a look at:
>
> https://github.com/ajaeger/ha-guide/tree/master/doc
>
> This one misses the top-level files that were in your directory but I
> can add them back later on.
>
> Sriram, do you have the perfect solution? ;)
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140914/8161295e/attachment-0001.html>

From aj at suse.com  Mon Sep 15 07:00:33 2014
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 15 Sep 2014 09:00:33 +0200
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
 team
In-Reply-To: <CAD0KtVFSUq_LKnOJLy9_3ubu0KczM7aU1Y9hcMn+H3b=jkaTew@mail.gmail.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
 <D0332543.83DD%edgar.magana@workday.com>
 <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>
 <5415EBB5.1000806@suse.com> <5415F849.9030405@suse.com>
 <CAD0KtVFSUq_LKnOJLy9_3ubu0KczM7aU1Y9hcMn+H3b=jkaTew@mail.gmail.com>
Message-ID: <54168E91.7060609@suse.com>

On 09/15/2014 01:24 AM, Anne Gentle wrote:
> Cool trick. :) I think I got it all but please do double-check:
> https://review.openstack.org/121426
> 
> The upstream this will pull from is https://github.com/annegentle/ha-guide

That one contains a lot more files toplevel than expected - did you
forget to *move* the files? Compare it with my version,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From sriram at sriramhere.com  Mon Sep 15 18:49:46 2014
From: sriram at sriramhere.com (Sriram Subramanian)
Date: Mon, 15 Sep 2014 14:49:46 -0400
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
	team
In-Reply-To: <54168E91.7060609@suse.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
 <D0332543.83DD%edgar.magana@workday.com>
 <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>
 <5415EBB5.1000806@suse.com> <5415F849.9030405@suse.com>
 <CAD0KtVFSUq_LKnOJLy9_3ubu0KczM7aU1Y9hcMn+H3b=jkaTew@mail.gmail.com>
 <54168E91.7060609@suse.com>
Message-ID: <CAP6wb7+aM5iYxiTsuxvhhSgUTt0=djcqAWwy5J=35VWo=4--7Q@mail.gmail.com>

Andreas,

You have glossary and pom. Anne's version is similar to your ha-guide
sub-directory below. I like how you retained the history.

.. <https://github.com/ajaeger/ha-guide>glossary
<https://github.com/ajaeger/ha-guide/tree/master/doc/glossary>Setup
ha-guide infrastructure
<https://github.com/ajaeger/ha-guide/commit/c6bf631ce7a19c363beebefb29bffc853764d569>an
hour agoha-guide
<https://github.com/ajaeger/ha-guide/tree/master/doc/ha-guide>Move to
doc/ha-guide subdir
<https://github.com/ajaeger/ha-guide/commit/149c3b3beb21ae8cd8bcae3a5799c40f5eef8270>22
hours agopom.xml
<https://github.com/ajaeger/ha-guide/blob/master/doc/pom.xml>Setup ha-guide
infrastructure
<https://github.com/ajaeger/ha-guide/commit/c6bf631ce7a19c363beebefb29bffc853764d569>an
hour ago

My understanding was we will end up having this document under
https://github.com/openstack/ha-doc, like
https://github.com/openstack/security-doc. Is that still correct?

thanks,
-Sriram



On Mon, Sep 15, 2014 at 3:00 AM, Andreas Jaeger <aj at suse.com> wrote:

> On 09/15/2014 01:24 AM, Anne Gentle wrote:
> > Cool trick. :) I think I got it all but please do double-check:
> > https://review.openstack.org/121426
> >
> > The upstream this will pull from is
> https://github.com/annegentle/ha-guide
>
> That one contains a lot more files toplevel than expected - did you
> forget to *move* the files? Compare it with my version,
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Thanks,
-Sriram
425-610-8465
www.sriramhere.com | www.clouddon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140915/6ef5e429/attachment.html>

From anne at openstack.org  Mon Sep 15 19:08:24 2014
From: anne at openstack.org (Anne Gentle)
Date: Mon, 15 Sep 2014 14:08:24 -0500
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
	team
In-Reply-To: <CAP6wb7+aM5iYxiTsuxvhhSgUTt0=djcqAWwy5J=35VWo=4--7Q@mail.gmail.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
 <D0332543.83DD%edgar.magana@workday.com>
 <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>
 <5415EBB5.1000806@suse.com> <5415F849.9030405@suse.com>
 <CAD0KtVFSUq_LKnOJLy9_3ubu0KczM7aU1Y9hcMn+H3b=jkaTew@mail.gmail.com>
 <54168E91.7060609@suse.com>
 <CAP6wb7+aM5iYxiTsuxvhhSgUTt0=djcqAWwy5J=35VWo=4--7Q@mail.gmail.com>
Message-ID: <CAD0KtVGR5gAxpBDU0E8y0x9f=LBb3m=ZuHH2aXp3ni2pUk=mbQ@mail.gmail.com>

On Mon, Sep 15, 2014 at 1:49 PM, Sriram Subramanian <sriram at sriramhere.com>
wrote:

> Andreas,
>
> You have glossary and pom. Anne's version is similar to your ha-guide
> sub-directory below. I like how you retained the history.
>
> .. <https://github.com/ajaeger/ha-guide>glossary
> <https://github.com/ajaeger/ha-guide/tree/master/doc/glossary>Setup
> ha-guide infrastructure
> <https://github.com/ajaeger/ha-guide/commit/c6bf631ce7a19c363beebefb29bffc853764d569>an
> hour agoha-guide
> <https://github.com/ajaeger/ha-guide/tree/master/doc/ha-guide>Move to
> doc/ha-guide subdir
> <https://github.com/ajaeger/ha-guide/commit/149c3b3beb21ae8cd8bcae3a5799c40f5eef8270>22
> hours agopom.xml
> <https://github.com/ajaeger/ha-guide/blob/master/doc/pom.xml>Setup
> ha-guide infrastructure
> <https://github.com/ajaeger/ha-guide/commit/c6bf631ce7a19c363beebefb29bffc853764d569>an
> hour ago
>
> My understanding was we will end up having this document under
> https://github.com/openstack/ha-doc, like
> https://github.com/openstack/security-doc. Is that still correct?
>

Yes, simply bike-shedding that it's ha-guide rather than ha-doc. The
Security "doc" had more than just the guide since they moved their security
notes into the repo as well, hence the "doc" name.


>
> thanks,
> -Sriram
>
>
>
> On Mon, Sep 15, 2014 at 3:00 AM, Andreas Jaeger <aj at suse.com> wrote:
>
>> On 09/15/2014 01:24 AM, Anne Gentle wrote:
>> > Cool trick. :) I think I got it all but please do double-check:
>> > https://review.openstack.org/121426
>> >
>> > The upstream this will pull from is
>> https://github.com/annegentle/ha-guide
>>
>> That one contains a lot more files toplevel than expected - did you
>> forget to *move* the files? Compare it with my version,
>>
>> Andreas
>> --
>>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
>
> --
> Thanks,
> -Sriram
> 425-610-8465
> www.sriramhere.com | www.clouddon.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140915/f048a435/attachment-0001.html>

From aj at suse.com  Mon Sep 15 19:15:19 2014
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 15 Sep 2014 21:15:19 +0200
Subject: [Openstack-docs] [Openstack-operators] High Availability Guide
	team
In-Reply-To: <CAP6wb7+aM5iYxiTsuxvhhSgUTt0=djcqAWwy5J=35VWo=4--7Q@mail.gmail.com>
References: <CAD0KtVE-7rHORJKkmqYzOZ=T2g8ySd_8WSwnEMuxwnsbw6O5mA@mail.gmail.com>
 <CAJfWK49CJ+7i5A8twGPcMWpq54jz2fZjvArytchfj5pQr4v0nw@mail.gmail.com>
 <D0332543.83DD%edgar.magana@workday.com>
 <CAD0KtVHEPy-MAt7pJTQNveA-VDNs3uL_iRHfm2fVhyp=g5E_Sg@mail.gmail.com>
 <5415EBB5.1000806@suse.com> <5415F849.9030405@suse.com>
 <CAD0KtVFSUq_LKnOJLy9_3ubu0KczM7aU1Y9hcMn+H3b=jkaTew@mail.gmail.com>
 <54168E91.7060609@suse.com>
 <CAP6wb7+aM5iYxiTsuxvhhSgUTt0=djcqAWwy5J=35VWo=4--7Q@mail.gmail.com>
Message-ID: <41eca3ad-262a-4d16-8f12-53b3bd41a023@email.android.com>

On 15. September 2014 20:49:46 MESZ, Sriram Subramanian <sriram at sriramhere.com> wrote:
>Andreas,
>
>You have glossary and pom. Anne's version is similar to your ha-guide
>sub-directory below. I like how you retained the history.
>
>.. <https://github.com/ajaeger/ha-guide>glossary
><https://github.com/ajaeger/ha-guide/tree/master/doc/glossary>Setup
>ha-guide infrastructure
><https://github.com/ajaeger/ha-guide/commit/c6bf631ce7a19c363beebefb29bffc853764d569>an
>hour agoha-guide
><https://github.com/ajaeger/ha-guide/tree/master/doc/ha-guide>Move to
>doc/ha-guide subdir
><https://github.com/ajaeger/ha-guide/commit/149c3b3beb21ae8cd8bcae3a5799c40f5eef8270>22
>hours agopom.xml
><https://github.com/ajaeger/ha-guide/blob/master/doc/pom.xml>Setup
>ha-guide
>infrastructure
><https://github.com/ajaeger/ha-guide/commit/c6bf631ce7a19c363beebefb29bffc853764d569>an
>hour ago
>
>My understanding was we will end up having this document under
>https://github.com/openstack/ha-doc, like
>https://github.com/openstack/security-doc. Is that still correct?
>
>thanks,
>-Sriram
>
>
>
>On Mon, Sep 15, 2014 at 3:00 AM, Andreas Jaeger <aj at suse.com> wrote:
>
>> On 09/15/2014 01:24 AM, Anne Gentle wrote:
>> > Cool trick. :) I think I got it all but please do double-check:
>> > https://review.openstack.org/121426
>> >
>> > The upstream this will pull from is
>> https://github.com/annegentle/ha-guide
>>
>> That one contains a lot more files toplevel than expected - did you
>> forget to *move* the files? Compare it with my version,
>>
>> Andreas
>> --
>>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG
>N?rnberg)
>>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272
>A126
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
>
>-- 
>Thanks,
>-Sriram
>425-610-8465
>www.sriramhere.com | www.clouddon.com

My repo is just the staging to import it into git.openstack.org which gets mirrored to github, 

Andreas 
-- 
Andreas Jaeger
aj@{suse.com,novell.com,opensuse.org} Twitter / Identica: jaegerandi
SUSE LINUX Products GmbH , Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) 
This email was sent from my phone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140915/32f6888e/attachment.html>

From amotoki at gmail.com  Tue Sep 16 13:54:36 2014
From: amotoki at gmail.com (Akihiro Motoki)
Date: Tue, 16 Sep 2014 22:54:36 +0900
Subject: [Openstack-docs] Tool to check help text in python clients?
Message-ID: <CALhU9tkzZVLUU0cVixiYH7fCNy7sC=f9s0cJA1QoYZMRfh6udg@mail.gmail.com>

Hi,

I sometimes see client library reviews which fix the help text punctuation
like https://review.openstack.org/#/c/119695/ .
Does the docs team have any tools to check it?
If so, it is nice to integrate it into pythonclient gate check.

Thanks,
Akihiro Motoki <amotoki at gmail.com>


From aj at suse.com  Tue Sep 16 15:01:46 2014
From: aj at suse.com (Andreas Jaeger)
Date: Tue, 16 Sep 2014 17:01:46 +0200
Subject: [Openstack-docs] Tool to check help text in python clients?
In-Reply-To: <CALhU9tkzZVLUU0cVixiYH7fCNy7sC=f9s0cJA1QoYZMRfh6udg@mail.gmail.com>
References: <CALhU9tkzZVLUU0cVixiYH7fCNy7sC=f9s0cJA1QoYZMRfh6udg@mail.gmail.com>
Message-ID: <541850DA.2060905@suse.com>

On 09/16/2014 03:54 PM, Akihiro Motoki wrote:
> Hi,
> 
> I sometimes see client library reviews which fix the help text punctuation
> like https://review.openstack.org/#/c/119695/ .
> Does the docs team have any tools to check it?
> If so, it is nice to integrate it into pythonclient gate check.

This is unfortunately a manual process ;(, checks would be appreciated.

Reviewing patches for the CLI guide like
https://review.openstack.org/#/c/121815, I notice the changes and then
take actions if something is missing.

For nova I added a hacking check once to check that the first letter is
capitalized (
https://review.openstack.org/#/c/67647/6/nova/hacking/checks.py ). Feel
free to build on this and add further checks,

Besides the oslo.config style guide, Diane wrote a more complex one for
CLI commands but gave up to get this in ;( See here for details
https://review.openstack.org/#/c/73015/

Any help here is welcome! Thanks for asking,
Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From mkassawara at gmail.com  Tue Sep 16 18:53:52 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Tue, 16 Sep 2014 13:53:52 -0500
Subject: [Openstack-docs] Install Guide Status
In-Reply-To: <1537181330.13478379.1410578401358.JavaMail.zimbra@redhat.com>
References: <541354AE.8050108@mirantis.com>
 <CABA+jQqbVoY3ky3NyUwGt3CyEsVLFWmmGcu1HR-Yq7wgdyjUzA@mail.gmail.com>
 <1537181330.13478379.1410578401358.JavaMail.zimbra@redhat.com>
Message-ID: <CABA+jQrbM0SCZYR0jQwEWaqdQDMoJL82nVLe-7yWNqp6HtO25w@mail.gmail.com>

Just a note for reviews... for all OpenStack services, I'm waiting on Juno
packages from distributions using systemd before updating service names and
start/enable instructions.

On Fri, Sep 12, 2014 at 10:20 PM, Steve Gordon <sgordon at redhat.com> wrote:

> ----- Original Message -----
> > From: "Matt Kassawara" <mkassawara at gmail.com>
> > To: "Nicholas Chase" <nchase at mirantis.com>
> >
> > I created a wiki page covering necessary changes (so far) for Juno based
> on
> > a combination of the following:
> >
> > 1) Configuration file changes from the configuration reference.
> > 2) Installation of "core" services on Ubuntu using Juno milestone 2
> > packages. Both the neutron and nova-network environments appear to work.
> > However, the milestone 2 packages don't fully support the [neutron]
> section
> > in nova.conf so the neutron environment uses a mixture of old and new
> > locations.
> >
> > Surprisingly, I didn't have to peek at gate configurations for hints.
> Also,
> > I'm still waiting on packages for RH/CentOS/Fedora and hope someone
> > familiar with SUSE and Debian can validate these changes well ahead of
> > release on 16 October.
>
> We're currently running CI on M-3 based packages for RDO. Unfortunately
> there has still been a heavy skew towards feature delivery in the last
> milestone in Juno (e.g. M-1: 4 blueprints, M-2: 8 blueprints, M-3 26:
> blueprints in Nova) so I would expect there is quite some potential for
> change there.
>
> -Steve
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140916/39b60edf/attachment.html>

From dazzachan at yahoo.com.au  Wed Sep 17 07:04:14 2014
From: dazzachan at yahoo.com.au (darren chan)
Date: Wed, 17 Sep 2014 00:04:14 -0700
Subject: [Openstack-docs] Review #119980
Message-ID: <1410937454.56431.YahooMailNeo@web160301.mail.bf1.yahoo.com>

Hi everyone,

I've submitted a patch which addresses a bug in the Havana documentation:
https://review.openstack.org/#/c/119980/


Can anyone confirm if this change can also be committed to master?

Cheers,
Darren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140917/d140e7ef/attachment.html>

From aj at suse.com  Wed Sep 17 09:36:27 2014
From: aj at suse.com (Andreas Jaeger)
Date: Wed, 17 Sep 2014 11:36:27 +0200
Subject: [Openstack-docs] Key or option in configuration files?
Message-ID: <5419561B.3000407@suse.com>

Reviewing
https://review.openstack.org/#/c/122027/

I noticed the usage of "key" but I see "option" used in other guides
when changing configuration files.

Example:
1) "Set auth_uri key to..."
2) "Set auth_uri option to..."

Is there a preferred way or is this something we use interchangeable?

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From anne at openstack.org  Wed Sep 17 13:06:34 2014
From: anne at openstack.org (Anne Gentle)
Date: Wed, 17 Sep 2014 08:06:34 -0500
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <5419561B.3000407@suse.com>
References: <5419561B.3000407@suse.com>
Message-ID: <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>

On Wed, Sep 17, 2014 at 4:36 AM, Andreas Jaeger <aj at suse.com> wrote:

> Reviewing
> https://review.openstack.org/#/c/122027/
>
> I noticed the usage of "key" but I see "option" used in other guides
> when changing configuration files.
>
> Example:
> 1) "Set auth_uri key to..."
> 2) "Set auth_uri option to..."
>
> Is there a preferred way or is this something we use interchangeable?
>
>
I'd prefer we stick to the option term consistently (even if it's a key
that goes into that option).


> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140917/1edefd09/attachment.html>

From mkassawara at gmail.com  Wed Sep 17 13:46:46 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Wed, 17 Sep 2014 08:46:46 -0500
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
References: <5419561B.3000407@suse.com>
 <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
Message-ID: <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>

Do we also prefer <option> over <literal> for them?

On Wed, Sep 17, 2014 at 8:06 AM, Anne Gentle <anne at openstack.org> wrote:

>
>
> On Wed, Sep 17, 2014 at 4:36 AM, Andreas Jaeger <aj at suse.com> wrote:
>
>> Reviewing
>> https://review.openstack.org/#/c/122027/
>>
>> I noticed the usage of "key" but I see "option" used in other guides
>> when changing configuration files.
>>
>> Example:
>> 1) "Set auth_uri key to..."
>> 2) "Set auth_uri option to..."
>>
>> Is there a preferred way or is this something we use interchangeable?
>>
>>
> I'd prefer we stick to the option term consistently (even if it's a key
> that goes into that option).
>
>
>> Andreas
>> --
>>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140917/4ab9f35a/attachment.html>

From anne at openstack.org  Wed Sep 17 15:54:52 2014
From: anne at openstack.org (Anne Gentle)
Date: Wed, 17 Sep 2014 10:54:52 -0500
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>
References: <5419561B.3000407@suse.com>
 <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
 <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>
Message-ID: <CAD0KtVEJNRp5K4c2ZjwmruL73PycrYdV3TpY-rQHFiynXzbdaw@mail.gmail.com>

On Wed, Sep 17, 2014 at 8:46 AM, Matt Kassawara <mkassawara at gmail.com>
wrote:

> Do we also prefer <option> over <literal> for them?
>

<option> is markup for inline options
https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Configuration_options_.28inline.29

<literal> is markup for inline code
https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Code_or_data_.28inline.29

Using <option> in this way would theoretically let us generate options
tables or pull out in other ways.



>
> On Wed, Sep 17, 2014 at 8:06 AM, Anne Gentle <anne at openstack.org> wrote:
>
>>
>>
>> On Wed, Sep 17, 2014 at 4:36 AM, Andreas Jaeger <aj at suse.com> wrote:
>>
>>> Reviewing
>>> https://review.openstack.org/#/c/122027/
>>>
>>> I noticed the usage of "key" but I see "option" used in other guides
>>> when changing configuration files.
>>>
>>> Example:
>>> 1) "Set auth_uri key to..."
>>> 2) "Set auth_uri option to..."
>>>
>>> Is there a preferred way or is this something we use interchangeable?
>>>
>>>
>> I'd prefer we stick to the option term consistently (even if it's a key
>> that goes into that option).
>>
>>
>>> Andreas
>>> --
>>>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>>>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>>>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>>>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>>>
>>> _______________________________________________
>>> Openstack-docs mailing list
>>> Openstack-docs at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>
>>
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140917/e480e313/attachment.html>

From mkassawara at gmail.com  Wed Sep 17 16:00:51 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Wed, 17 Sep 2014 11:00:51 -0500
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <CAD0KtVEJNRp5K4c2ZjwmruL73PycrYdV3TpY-rQHFiynXzbdaw@mail.gmail.com>
References: <5419561B.3000407@suse.com>
 <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
 <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>
 <CAD0KtVEJNRp5K4c2ZjwmruL73PycrYdV3TpY-rQHFiynXzbdaw@mail.gmail.com>
Message-ID: <CABA+jQrNt=wkQsOtd-nH0kn7iDHWB25B5QHjAJ_HYZjO-nBeZQ@mail.gmail.com>

That... did not help me.

On Wed, Sep 17, 2014 at 10:54 AM, Anne Gentle <anne at openstack.org> wrote:

>
>
> On Wed, Sep 17, 2014 at 8:46 AM, Matt Kassawara <mkassawara at gmail.com>
> wrote:
>
>> Do we also prefer <option> over <literal> for them?
>>
>
> <option> is markup for inline options
>
> https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Configuration_options_.28inline.29
>
> <literal> is markup for inline code
>
> https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Code_or_data_.28inline.29
>
> Using <option> in this way would theoretically let us generate options
> tables or pull out in other ways.
>
>
>
>>
>> On Wed, Sep 17, 2014 at 8:06 AM, Anne Gentle <anne at openstack.org> wrote:
>>
>>>
>>>
>>> On Wed, Sep 17, 2014 at 4:36 AM, Andreas Jaeger <aj at suse.com> wrote:
>>>
>>>> Reviewing
>>>> https://review.openstack.org/#/c/122027/
>>>>
>>>> I noticed the usage of "key" but I see "option" used in other guides
>>>> when changing configuration files.
>>>>
>>>> Example:
>>>> 1) "Set auth_uri key to..."
>>>> 2) "Set auth_uri option to..."
>>>>
>>>> Is there a preferred way or is this something we use interchangeable?
>>>>
>>>>
>>> I'd prefer we stick to the option term consistently (even if it's a key
>>> that goes into that option).
>>>
>>>
>>>> Andreas
>>>> --
>>>>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>>>>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>>>>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>>>>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>>>>
>>>> _______________________________________________
>>>> Openstack-docs mailing list
>>>> Openstack-docs at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>>
>>>
>>>
>>> _______________________________________________
>>> Openstack-docs mailing list
>>> Openstack-docs at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140917/3c5e68d7/attachment-0001.html>

From anne at openstack.org  Wed Sep 17 16:06:53 2014
From: anne at openstack.org (Anne Gentle)
Date: Wed, 17 Sep 2014 11:06:53 -0500
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <CABA+jQrNt=wkQsOtd-nH0kn7iDHWB25B5QHjAJ_HYZjO-nBeZQ@mail.gmail.com>
References: <5419561B.3000407@suse.com>
 <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
 <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>
 <CAD0KtVEJNRp5K4c2ZjwmruL73PycrYdV3TpY-rQHFiynXzbdaw@mail.gmail.com>
 <CABA+jQrNt=wkQsOtd-nH0kn7iDHWB25B5QHjAJ_HYZjO-nBeZQ@mail.gmail.com>
Message-ID: <CAD0KtVHavr+HUkLbgF1G51e1ZEAt=4Es2JhmVLxNSTO48_yK=g@mail.gmail.com>

Heh.

Okay, I don't see the value in changing all of our source at this point.
Here's an example though.

This example of literal markup shows an inline "code" (ok, weak example)
marking. The nova user is not an option, but we do want to set it off as
it's the name we expect.

<para>Replace <replaceable>NOVA_PASS</replaceable> with the password you
chose for the <literal>nova</literal> user in the Identity service.</para>

In the example below, if we would use <option> instead of <literal> we
could one day automate a list of options described in the install guide:

<note><para>Comment out any <literal>auth_host</literal>,
<literal>auth_port</literal>, and <literal>auth_protocol</literal> options
because the <literal>identity_uri</literal> option replaces
them.</para></note>

I really don't think the difference is worth the trouble in changing the
current source though.

On Wed, Sep 17, 2014 at 11:00 AM, Matt Kassawara <mkassawara at gmail.com>
wrote:

> That... did not help me.
>
> On Wed, Sep 17, 2014 at 10:54 AM, Anne Gentle <anne at openstack.org> wrote:
>
>>
>>
>> On Wed, Sep 17, 2014 at 8:46 AM, Matt Kassawara <mkassawara at gmail.com>
>> wrote:
>>
>>> Do we also prefer <option> over <literal> for them?
>>>
>>
>> <option> is markup for inline options
>>
>> https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Configuration_options_.28inline.29
>>
>> <literal> is markup for inline code
>>
>> https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Code_or_data_.28inline.29
>>
>> Using <option> in this way would theoretically let us generate options
>> tables or pull out in other ways.
>>
>>
>>
>>>
>>> On Wed, Sep 17, 2014 at 8:06 AM, Anne Gentle <anne at openstack.org> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Sep 17, 2014 at 4:36 AM, Andreas Jaeger <aj at suse.com> wrote:
>>>>
>>>>> Reviewing
>>>>> https://review.openstack.org/#/c/122027/
>>>>>
>>>>> I noticed the usage of "key" but I see "option" used in other guides
>>>>> when changing configuration files.
>>>>>
>>>>> Example:
>>>>> 1) "Set auth_uri key to..."
>>>>> 2) "Set auth_uri option to..."
>>>>>
>>>>> Is there a preferred way or is this something we use interchangeable?
>>>>>
>>>>>
>>>> I'd prefer we stick to the option term consistently (even if it's a key
>>>> that goes into that option).
>>>>
>>>>
>>>>> Andreas
>>>>> --
>>>>>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>>>>>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>>>>>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG
>>>>> N?rnberg)
>>>>>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272
>>>>> A126
>>>>>
>>>>> _______________________________________________
>>>>> Openstack-docs mailing list
>>>>> Openstack-docs at lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Openstack-docs mailing list
>>>> Openstack-docs at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140917/e5ba4373/attachment.html>

From aj at suse.com  Wed Sep 17 16:13:47 2014
From: aj at suse.com (Andreas Jaeger)
Date: Wed, 17 Sep 2014 18:13:47 +0200
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <CAD0KtVHavr+HUkLbgF1G51e1ZEAt=4Es2JhmVLxNSTO48_yK=g@mail.gmail.com>
References: <5419561B.3000407@suse.com>
 <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
 <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>
 <CAD0KtVEJNRp5K4c2ZjwmruL73PycrYdV3TpY-rQHFiynXzbdaw@mail.gmail.com>
 <CABA+jQrNt=wkQsOtd-nH0kn7iDHWB25B5QHjAJ_HYZjO-nBeZQ@mail.gmail.com>
 <CAD0KtVHavr+HUkLbgF1G51e1ZEAt=4Es2JhmVLxNSTO48_yK=g@mail.gmail.com>
Message-ID: <5419B33B.4030607@suse.com>

On 09/17/2014 06:06 PM, Anne Gentle wrote:
> Heh.
> 
> Okay, I don't see the value in changing all of our source at this point.
> Here's an example though.
> 
> This example of literal markup shows an inline "code" (ok, weak example)
> marking. The nova user is not an option, but we do want to set it off as
> it's the name we expect.
> 
> <para>Replace <replaceable>NOVA_PASS</replaceable> with the password you
> chose for the <literal>nova</literal> user in the Identity service.</para>
> 
> In the example below, if we would use <option> instead of <literal> we
> could one day automate a list of options described in the install guide:
> 
> <note><para>Comment out any <literal>auth_host</literal>,
> <literal>auth_port</literal>, and <literal>auth_protocol</literal>
> options because the <literal>identity_uri</literal> option replaces
> them.</para></note>
> 
> I really don't think the difference is worth the trouble in changing the
> current source though.


So, new code should use <option>option</option> but old code with
<literal> - also with key? is fine...

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From mkassawara at gmail.com  Wed Sep 17 16:24:09 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Wed, 17 Sep 2014 11:24:09 -0500
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <5419B33B.4030607@suse.com>
References: <5419561B.3000407@suse.com>
 <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
 <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>
 <CAD0KtVEJNRp5K4c2ZjwmruL73PycrYdV3TpY-rQHFiynXzbdaw@mail.gmail.com>
 <CABA+jQrNt=wkQsOtd-nH0kn7iDHWB25B5QHjAJ_HYZjO-nBeZQ@mail.gmail.com>
 <CAD0KtVHavr+HUkLbgF1G51e1ZEAt=4Es2JhmVLxNSTO48_yK=g@mail.gmail.com>
 <5419B33B.4030607@suse.com>
Message-ID: <CABA+jQpTLT4qHF1iY9TWpG0=uAjK4O+Bmc7DZUDivq06w5+reg@mail.gmail.com>

I've seen a few cases of <literal> vs. <option> recently appear in reviews
and we need a decision either way. The convention definitions and examples
don't compel me to change <literal> to <option>.

On Wed, Sep 17, 2014 at 11:13 AM, Andreas Jaeger <aj at suse.com> wrote:

> On 09/17/2014 06:06 PM, Anne Gentle wrote:
> > Heh.
> >
> > Okay, I don't see the value in changing all of our source at this point.
> > Here's an example though.
> >
> > This example of literal markup shows an inline "code" (ok, weak example)
> > marking. The nova user is not an option, but we do want to set it off as
> > it's the name we expect.
> >
> > <para>Replace <replaceable>NOVA_PASS</replaceable> with the password you
> > chose for the <literal>nova</literal> user in the Identity
> service.</para>
> >
> > In the example below, if we would use <option> instead of <literal> we
> > could one day automate a list of options described in the install guide:
> >
> > <note><para>Comment out any <literal>auth_host</literal>,
> > <literal>auth_port</literal>, and <literal>auth_protocol</literal>
> > options because the <literal>identity_uri</literal> option replaces
> > them.</para></note>
> >
> > I really don't think the difference is worth the trouble in changing the
> > current source though.
>
>
> So, new code should use <option>option</option> but old code with
> <literal> - also with key? is fine...
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140917/43be7e6c/attachment.html>

From aj at suse.com  Thu Sep 18 06:03:00 2014
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 18 Sep 2014 08:03:00 +0200
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <CABA+jQpTLT4qHF1iY9TWpG0=uAjK4O+Bmc7DZUDivq06w5+reg@mail.gmail.com>
References: <5419561B.3000407@suse.com>
 <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
 <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>
 <CAD0KtVEJNRp5K4c2ZjwmruL73PycrYdV3TpY-rQHFiynXzbdaw@mail.gmail.com>
 <CABA+jQrNt=wkQsOtd-nH0kn7iDHWB25B5QHjAJ_HYZjO-nBeZQ@mail.gmail.com>
 <CAD0KtVHavr+HUkLbgF1G51e1ZEAt=4Es2JhmVLxNSTO48_yK=g@mail.gmail.com>
 <5419B33B.4030607@suse.com>
 <CABA+jQpTLT4qHF1iY9TWpG0=uAjK4O+Bmc7DZUDivq06w5+reg@mail.gmail.com>
Message-ID: <541A7594.9040002@suse.com>

On 09/17/2014 06:24 PM, Matt Kassawara wrote:
> I've seen a few cases of <literal> vs. <option> recently appear in
> reviews and we need a decision either way. The convention definitions
> and examples don't compel me to change <literal> to <option>.
> 

Let's be pragmatic:

If you write new docs, use <option>, if you copy & paste text around,
leave it as is...

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Thu Sep 18 07:23:12 2014
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 18 Sep 2014 09:23:12 +0200
Subject: [Openstack-docs] Key or option in configuration files?
In-Reply-To: <541A7594.9040002@suse.com>
References: <5419561B.3000407@suse.com>
 <CAD0KtVG1d8GDQFez0a6sr14u7w8GvCoiwJN-FSDctVhTrOr3aA@mail.gmail.com>
 <CABA+jQp_o1Hx2e0YOvHPy7S1C2YJKbaH+oVA2a16e580B_35KA@mail.gmail.com>
 <CAD0KtVEJNRp5K4c2ZjwmruL73PycrYdV3TpY-rQHFiynXzbdaw@mail.gmail.com>
 <CABA+jQrNt=wkQsOtd-nH0kn7iDHWB25B5QHjAJ_HYZjO-nBeZQ@mail.gmail.com>
 <CAD0KtVHavr+HUkLbgF1G51e1ZEAt=4Es2JhmVLxNSTO48_yK=g@mail.gmail.com>
 <5419B33B.4030607@suse.com>
 <CABA+jQpTLT4qHF1iY9TWpG0=uAjK4O+Bmc7DZUDivq06w5+reg@mail.gmail.com>
 <541A7594.9040002@suse.com>
Message-ID: <541A8860.70308@suse.com>

Conventions link:

https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Configuration_options_.28inline.29

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From tomo at dream.daynight.jp  Thu Sep 18 12:37:23 2014
From: tomo at dream.daynight.jp (KATO Tomoyuki)
Date: Thu, 18 Sep 2014 21:37:23 +0900
Subject: [Openstack-docs] [TG] reference to old training guides
Message-ID: <201409181237.s8ICbNxR005873@www2826.sakura.ne.jp>

Hi,

We sometimes receive bug reports for old Training Guides (for example, [1]).
For example, old contents [2] were moved to new guides [3][4],
and the reported bugs had been already fixed when bugs were reported.

I wonder if somewhere link to old training guides?

thought?

[1] https://bugs.launchpad.net/openstack-training-guides/+bug/1370676
[2] http://docs.openstack.org/training-guides/content/module001-ch006-overview-horizon-cli.html
[3] http://docs.openstack.org/training-guides/content/associate-controller-node.html#associate-overview-horizon-cli
[4] http://docs.openstack.org/training-guides/content/operator-controller-node.html#operator-overview-horizon-cli

--
KATO Tomoyuki


From anne at openstack.org  Thu Sep 18 13:49:11 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 18 Sep 2014 08:49:11 -0500
Subject: [Openstack-docs] [TG] reference to old training guides
In-Reply-To: <201409181237.s8ICbNxR005873@www2826.sakura.ne.jp>
References: <201409181237.s8ICbNxR005873@www2826.sakura.ne.jp>
Message-ID: <CAD0KtVGoo9anMgxgdDQvBZgVO6gvc5CwcrGvGYCNhse_0Gd6zw@mail.gmail.com>

Thanks for asking.

While we are fixing the problem of old content staying on the server, for
now the fix is a manual one. I'll log onto the FTP server now and delete
old files.

Thanks for reporting -
Anne

On Thu, Sep 18, 2014 at 7:37 AM, KATO Tomoyuki <tomo at dream.daynight.jp>
wrote:

> Hi,
>
> We sometimes receive bug reports for old Training Guides (for example,
> [1]).
> For example, old contents [2] were moved to new guides [3][4],
> and the reported bugs had been already fixed when bugs were reported.
>
> I wonder if somewhere link to old training guides?
>
> thought?
>
> [1] https://bugs.launchpad.net/openstack-training-guides/+bug/1370676
> [2]
> http://docs.openstack.org/training-guides/content/module001-ch006-overview-horizon-cli.html
> [3]
> http://docs.openstack.org/training-guides/content/associate-controller-node.html#associate-overview-horizon-cli
> [4]
> http://docs.openstack.org/training-guides/content/operator-controller-node.html#operator-overview-horizon-cli
>
> --
> KATO Tomoyuki
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140918/ebef6530/attachment.html>

From mkassawara at gmail.com  Thu Sep 18 16:02:29 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Thu, 18 Sep 2014 11:02:29 -0500
Subject: [Openstack-docs] Example command output with e-mail address
Message-ID: <CABA+jQoTeFEh6ZvSvwRc-1Q5gX_Yvu6589iXw+ia+rPGYM+H6Q@mail.gmail.com>

The review process for [1] contains some discussion about example command
output that includes an e-mail address when we use a <replaceable> for it.
For example, we tell the user to replace EMAIL_ADDRESS with a suitable
e-mail address, but the example command uses "service at example.com" to
reduce field alignment issues with <computeroutput>. Upon further
investigation, I determined that the "keystone user-create" command doesn't
require an e-mail address and it don't make sense for services anyway. Why
don't we remove the e-mail address option from user creation steps... at
least for services?

[1] https://review.openstack.org/#/c/122027/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140918/8e90370e/attachment.html>

From aj at suse.com  Thu Sep 18 17:24:23 2014
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 18 Sep 2014 19:24:23 +0200
Subject: [Openstack-docs] Example command output with e-mail address
In-Reply-To: <CABA+jQoTeFEh6ZvSvwRc-1Q5gX_Yvu6589iXw+ia+rPGYM+H6Q@mail.gmail.com>
References: <CABA+jQoTeFEh6ZvSvwRc-1Q5gX_Yvu6589iXw+ia+rPGYM+H6Q@mail.gmail.com>
Message-ID: <541B1547.5000104@suse.com>

On 09/18/2014 06:02 PM, Matt Kassawara wrote:
> The review process for [1] contains some discussion about example
> command output that includes an e-mail address when we use a
> <replaceable> for it. For example, we tell the user to replace
> EMAIL_ADDRESS with a suitable e-mail address, but the example command
> uses "service at example.com <mailto:service at example.com>" to reduce field
> alignment issues with <computeroutput>. Upon further investigation, I
> determined that the "keystone user-create" command doesn't require an
> e-mail address and it don't make sense for services anyway. Why don't we
> remove the e-mail address option from user creation steps... at least
> for services?
> 
> [1] https://review.openstack.org/#/c/122027/

If it works, I'm fine with leaving it out...

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From anne at openstack.org  Thu Sep 18 18:37:12 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 18 Sep 2014 13:37:12 -0500
Subject: [Openstack-docs] [TG] reference to old training guides
In-Reply-To: <CAD0KtVGoo9anMgxgdDQvBZgVO6gvc5CwcrGvGYCNhse_0Gd6zw@mail.gmail.com>
References: <201409181237.s8ICbNxR005873@www2826.sakura.ne.jp>
 <CAD0KtVGoo9anMgxgdDQvBZgVO6gvc5CwcrGvGYCNhse_0Gd6zw@mail.gmail.com>
Message-ID: <CAD0KtVGBY0D1Xe6XYeSEJ_V-nNrN5iHvzgbn+Vvz_3tvqdQR=g@mail.gmail.com>

More comments on the bug itself, but thought I'd also bring it up here for
more eyes. I deleted the file mentioned in the bug. However there are many
files with a Jan 31 2014 date like this one, should they all be deleted?

There are many other files with a Jul 21 2014 date, should those be deleted?

Thanks,
Anne

On Thu, Sep 18, 2014 at 8:49 AM, Anne Gentle <anne at openstack.org> wrote:

> Thanks for asking.
>
> While we are fixing the problem of old content staying on the server, for
> now the fix is a manual one. I'll log onto the FTP server now and delete
> old files.
>
> Thanks for reporting -
> Anne
>
> On Thu, Sep 18, 2014 at 7:37 AM, KATO Tomoyuki <tomo at dream.daynight.jp>
> wrote:
>
>> Hi,
>>
>> We sometimes receive bug reports for old Training Guides (for example,
>> [1]).
>> For example, old contents [2] were moved to new guides [3][4],
>> and the reported bugs had been already fixed when bugs were reported.
>>
>> I wonder if somewhere link to old training guides?
>>
>> thought?
>>
>> [1] https://bugs.launchpad.net/openstack-training-guides/+bug/1370676
>> [2]
>> http://docs.openstack.org/training-guides/content/module001-ch006-overview-horizon-cli.html
>> [3]
>> http://docs.openstack.org/training-guides/content/associate-controller-node.html#associate-overview-horizon-cli
>> [4]
>> http://docs.openstack.org/training-guides/content/operator-controller-node.html#operator-overview-horizon-cli
>>
>> --
>> KATO Tomoyuki
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140918/1d53d27b/attachment.html>

From seanroberts66 at gmail.com  Thu Sep 18 19:57:35 2014
From: seanroberts66 at gmail.com (Sean Roberts)
Date: Thu, 18 Sep 2014 12:57:35 -0700
Subject: [Openstack-docs] [TG] reference to old training guides
In-Reply-To: <CAD0KtVGoo9anMgxgdDQvBZgVO6gvc5CwcrGvGYCNhse_0Gd6zw@mail.gmail.com>
References: <201409181237.s8ICbNxR005873@www2826.sakura.ne.jp>
 <CAD0KtVGoo9anMgxgdDQvBZgVO6gvc5CwcrGvGYCNhse_0Gd6zw@mail.gmail.com>
Message-ID: <CD5C6F1F-EC5C-4326-B9F1-E231774C3774@gmail.com>

Thanks!

~sean

> On Sep 18, 2014, at 6:49 AM, Anne Gentle <anne at openstack.org> wrote:
> 
> Thanks for asking. 
> 
> While we are fixing the problem of old content staying on the server, for now the fix is a manual one. I'll log onto the FTP server now and delete old files. 
> 
> Thanks for reporting -
> Anne
> 
>> On Thu, Sep 18, 2014 at 7:37 AM, KATO Tomoyuki <tomo at dream.daynight.jp> wrote:
>> Hi,
>> 
>> We sometimes receive bug reports for old Training Guides (for example, [1]).
>> For example, old contents [2] were moved to new guides [3][4],
>> and the reported bugs had been already fixed when bugs were reported.
>> 
>> I wonder if somewhere link to old training guides?
>> 
>> thought?
>> 
>> [1] https://bugs.launchpad.net/openstack-training-guides/+bug/1370676
>> [2] http://docs.openstack.org/training-guides/content/module001-ch006-overview-horizon-cli.html
>> [3] http://docs.openstack.org/training-guides/content/associate-controller-node.html#associate-overview-horizon-cli
>> [4] http://docs.openstack.org/training-guides/content/operator-controller-node.html#operator-overview-horizon-cli
>> 
>> --
>> KATO Tomoyuki
>> 
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140918/2fb10001/attachment-0001.html>

From seanroberts66 at gmail.com  Thu Sep 18 19:59:27 2014
From: seanroberts66 at gmail.com (Sean Roberts)
Date: Thu, 18 Sep 2014 12:59:27 -0700
Subject: [Openstack-docs] [TG] reference to old training guides
In-Reply-To: <CAD0KtVGBY0D1Xe6XYeSEJ_V-nNrN5iHvzgbn+Vvz_3tvqdQR=g@mail.gmail.com>
References: <201409181237.s8ICbNxR005873@www2826.sakura.ne.jp>
 <CAD0KtVGoo9anMgxgdDQvBZgVO6gvc5CwcrGvGYCNhse_0Gd6zw@mail.gmail.com>
 <CAD0KtVGBY0D1Xe6XYeSEJ_V-nNrN5iHvzgbn+Vvz_3tvqdQR=g@mail.gmail.com>
Message-ID: <FEDBE470-D102-47FC-9F6D-EA819F3C8BD0@gmail.com>

I'll need to take a closer look. Would the time stamp on the remote server be exactly the same as the repo?

~sean

> On Sep 18, 2014, at 11:37 AM, Anne Gentle <anne at openstack.org> wrote:
> 
> More comments on the bug itself, but thought I'd also bring it up here for more eyes. I deleted the file mentioned in the bug. However there are many files with a Jan 31 2014 date like this one, should they all be deleted?
> 
> There are many other files with a Jul 21 2014 date, should those be deleted?
> 
> Thanks,
> Anne
> 
>> On Thu, Sep 18, 2014 at 8:49 AM, Anne Gentle <anne at openstack.org> wrote:
>> Thanks for asking. 
>> 
>> While we are fixing the problem of old content staying on the server, for now the fix is a manual one. I'll log onto the FTP server now and delete old files. 
>> 
>> Thanks for reporting -
>> Anne
>> 
>>> On Thu, Sep 18, 2014 at 7:37 AM, KATO Tomoyuki <tomo at dream.daynight.jp> wrote:
>>> Hi,
>>> 
>>> We sometimes receive bug reports for old Training Guides (for example, [1]).
>>> For example, old contents [2] were moved to new guides [3][4],
>>> and the reported bugs had been already fixed when bugs were reported.
>>> 
>>> I wonder if somewhere link to old training guides?
>>> 
>>> thought?
>>> 
>>> [1] https://bugs.launchpad.net/openstack-training-guides/+bug/1370676
>>> [2] http://docs.openstack.org/training-guides/content/module001-ch006-overview-horizon-cli.html
>>> [3] http://docs.openstack.org/training-guides/content/associate-controller-node.html#associate-overview-horizon-cli
>>> [4] http://docs.openstack.org/training-guides/content/operator-controller-node.html#operator-overview-horizon-cli
>>> 
>>> --
>>> KATO Tomoyuki
>>> 
>>> _______________________________________________
>>> Openstack-docs mailing list
>>> Openstack-docs at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140918/b9491fff/attachment.html>

From anne at openstack.org  Thu Sep 18 19:59:11 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 18 Sep 2014 14:59:11 -0500
Subject: [Openstack-docs] What's up doc? Sept 18 2014
Message-ID: <CAD0KtVGnzWzJBOsobNPkzp6ehPjkkMuOFyyk3FBdVw-BwWO65g@mail.gmail.com>

We're less than a month from our October 16th release and I'm appreciating
the focus on the install guide. Thanks Matt Kassawara and our intrepid
reviewers!

Tomorrow we should have a release 2.1.3 of the clouddocs-maven-plugin. This
is the version we'll "freeze" upon for the upcoming Juno release. Sorry,
epub didn't get in for this release. One noticeable change for the API
Reference is the addition of short titles added to the description of each
API call. I believe this makes it easier to talk about a single API call so
I appreciate the input going into that.

The HOT Template Guide is coming along nicely.

I've had a request to look into automating pulling out system usage data
from nova for starters and glance and other projects. Right now it's all
gathered in https://wiki.openstack.org/wiki/SystemUsageData. I thought I'd
start here to see who might have automation ideas. We'll find a landing
spot in one of the existing guides for this info. This isn't for the Juno
release but something to consider for Kilo.

I've been working with Tom on a redesign document to list requirements for
a redesign so that we can have a page-based way to view OpenStack docs.
I've been working on it for a couple months so I'd like to move it forward
in the community. It's in Google Docs right now. I'll discuss at the next
team meeting... speaking of... Next week I'm at an internal conference and
can't run the weekly Doc Team meeting at the scheduled time, but I'd really
like to reschedule to another day since we're in a crunch period. Would
Monday work instead? Let me know.

Thanks,
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140918/cffe9211/attachment.html>

From anne at openstack.org  Thu Sep 18 20:02:08 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 18 Sep 2014 15:02:08 -0500
Subject: [Openstack-docs] [TG] reference to old training guides
In-Reply-To: <FEDBE470-D102-47FC-9F6D-EA819F3C8BD0@gmail.com>
References: <201409181237.s8ICbNxR005873@www2826.sakura.ne.jp>
 <CAD0KtVGoo9anMgxgdDQvBZgVO6gvc5CwcrGvGYCNhse_0Gd6zw@mail.gmail.com>
 <CAD0KtVGBY0D1Xe6XYeSEJ_V-nNrN5iHvzgbn+Vvz_3tvqdQR=g@mail.gmail.com>
 <FEDBE470-D102-47FC-9F6D-EA819F3C8BD0@gmail.com>
Message-ID: <CAD0KtVHyDKFGmKB6EkuSqe49M3O1ijJEM7Rvp8CAF0DVw=zz=w@mail.gmail.com>

The time stamp indicates when it was built. When filenames change or xml:id
change, the HTML file name can be changed as well, so the newer HTML file
output is usually the most accurate.

On Thu, Sep 18, 2014 at 2:59 PM, Sean Roberts <seanroberts66 at gmail.com>
wrote:

> I'll need to take a closer look. Would the time stamp on the remote server
> be exactly the same as the repo?
>
> ~sean
>
> On Sep 18, 2014, at 11:37 AM, Anne Gentle <anne at openstack.org> wrote:
>
> More comments on the bug itself, but thought I'd also bring it up here for
> more eyes. I deleted the file mentioned in the bug. However there are many
> files with a Jan 31 2014 date like this one, should they all be deleted?
>
> There are many other files with a Jul 21 2014 date, should those be
> deleted?
>
> Thanks,
> Anne
>
> On Thu, Sep 18, 2014 at 8:49 AM, Anne Gentle <anne at openstack.org> wrote:
>
>> Thanks for asking.
>>
>> While we are fixing the problem of old content staying on the server, for
>> now the fix is a manual one. I'll log onto the FTP server now and delete
>> old files.
>>
>> Thanks for reporting -
>> Anne
>>
>> On Thu, Sep 18, 2014 at 7:37 AM, KATO Tomoyuki <tomo at dream.daynight.jp>
>> wrote:
>>
>>> Hi,
>>>
>>> We sometimes receive bug reports for old Training Guides (for example,
>>> [1]).
>>> For example, old contents [2] were moved to new guides [3][4],
>>> and the reported bugs had been already fixed when bugs were reported.
>>>
>>> I wonder if somewhere link to old training guides?
>>>
>>> thought?
>>>
>>> [1] https://bugs.launchpad.net/openstack-training-guides/+bug/1370676
>>> [2]
>>> http://docs.openstack.org/training-guides/content/module001-ch006-overview-horizon-cli.html
>>> [3]
>>> http://docs.openstack.org/training-guides/content/associate-controller-node.html#associate-overview-horizon-cli
>>> [4]
>>> http://docs.openstack.org/training-guides/content/operator-controller-node.html#operator-overview-horizon-cli
>>>
>>> --
>>> KATO Tomoyuki
>>>
>>> _______________________________________________
>>> Openstack-docs mailing list
>>> Openstack-docs at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>
>>
>>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140918/e59da895/attachment.html>

From aj at suse.com  Fri Sep 19 07:22:01 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 19 Sep 2014 09:22:01 +0200
Subject: [Openstack-docs] Freeze ha-guide
Message-ID: <541BD999.5070502@suse.com>

In preparation for splitting up the ha-guide, I suggest to freeze the
guide in openstack-manuals...

Let's do further patches to it once the new repository is setup which
should happen really soon now,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From berendt at b1-systems.de  Fri Sep 19 08:02:37 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Fri, 19 Sep 2014 10:02:37 +0200
Subject: [Openstack-docs] Freeze ha-guide
In-Reply-To: <541BD999.5070502@suse.com>
References: <541BD999.5070502@suse.com>
Message-ID: <541BE31D.7040703@b1-systems.de>

On 09/19/2014 09:22 AM, Andreas Jaeger wrote:
> In preparation for splitting up the ha-guide, I suggest to freeze the
> guide in openstack-manuals...

+1

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From anne at openstack.org  Fri Sep 19 12:16:47 2014
From: anne at openstack.org (Anne Gentle)
Date: Fri, 19 Sep 2014 07:16:47 -0500
Subject: [Openstack-docs] Freeze ha-guide
In-Reply-To: <541BE31D.7040703@b1-systems.de>
References: <541BD999.5070502@suse.com> <541BE31D.7040703@b1-systems.de>
Message-ID: <CAD0KtVEoRYmfE3ndbnq6Tz_X_K8wheuTWMC0yzce8HV-hheGWw@mail.gmail.com>

On Fri, Sep 19, 2014 at 3:02 AM, Christian Berendt <berendt at b1-systems.de>
wrote:

> On 09/19/2014 09:22 AM, Andreas Jaeger wrote:
> > In preparation for splitting up the ha-guide, I suggest to freeze the
> > guide in openstack-manuals...
>
> +1
>

Yep, sounds good. By freeze you mean -2 any patches against
openstack-manuals, telling the author that the other repo is where it'll
go, right?


>
> --
> Christian Berendt
> Cloud Solution Architect
> Mail: berendt at b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140919/ed9dbb75/attachment.html>

From aj at suse.com  Fri Sep 19 14:08:05 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 19 Sep 2014 16:08:05 +0200
Subject: [Openstack-docs] new ha-guide is setup
Message-ID: <541C38C5.40808@suse.com>

The new ha-guide repository is setup, you can clone it now.

The ACLs need setup and I expect we need an initial patch to get
everything working as it should. I'll try to do this tonight but if
anybody else wants to start directly, speak up here and go for it,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Fri Sep 19 14:08:48 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 19 Sep 2014 16:08:48 +0200
Subject: [Openstack-docs] Freeze ha-guide
In-Reply-To: <CAD0KtVEoRYmfE3ndbnq6Tz_X_K8wheuTWMC0yzce8HV-hheGWw@mail.gmail.com>
References: <541BD999.5070502@suse.com> <541BE31D.7040703@b1-systems.de>
 <CAD0KtVEoRYmfE3ndbnq6Tz_X_K8wheuTWMC0yzce8HV-hheGWw@mail.gmail.com>
Message-ID: <541C38F0.4040809@suse.com>

On 09/19/2014 02:16 PM, Anne Gentle wrote:
> 
> 
> On Fri, Sep 19, 2014 at 3:02 AM, Christian Berendt
> <berendt at b1-systems.de <mailto:berendt at b1-systems.de>> wrote:
> 
>     On 09/19/2014 09:22 AM, Andreas Jaeger wrote:
>     > In preparation for splitting up the ha-guide, I suggest to freeze the
>     > guide in openstack-manuals...
> 
>     +1
> 
> 
> Yep, sounds good. By freeze you mean -2 any patches against
> openstack-manuals, telling the author that the other repo is where it'll
> go, right?

Correct.

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From anne at openstack.org  Fri Sep 19 14:13:21 2014
From: anne at openstack.org (Anne Gentle)
Date: Fri, 19 Sep 2014 09:13:21 -0500
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <541C38C5.40808@suse.com>
References: <541C38C5.40808@suse.com>
Message-ID: <CAD0KtVH_gP1rhV-UvkZOrHcJwNHgDN3Qhe7sNOCoqSx8ZsDQJQ@mail.gmail.com>

I'll do the removal patch from openstack-manuals.

I'm not completely sure how to set up ACL, so I would need help. I'll start
the patch that removes, though.

On Fri, Sep 19, 2014 at 9:08 AM, Andreas Jaeger <aj at suse.com> wrote:

> The new ha-guide repository is setup, you can clone it now.
>
> The ACLs need setup and I expect we need an initial patch to get
> everything working as it should. I'll try to do this tonight but if
> anybody else wants to start directly, speak up here and go for it,
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140919/be8d07fa/attachment.html>

From aj at suse.com  Fri Sep 19 15:04:09 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 19 Sep 2014 17:04:09 +0200
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <541C38C5.40808@suse.com>
References: <541C38C5.40808@suse.com>
Message-ID: <541C45E9.2040102@suse.com>

On 09/19/2014 04:08 PM, Andreas Jaeger wrote:
> The new ha-guide repository is setup, you can clone it now.
> 
> The ACLs need setup and I expect we need an initial patch to get
> everything working as it should. I'll try to do this tonight but if
> anybody else wants to start directly, speak up here and go for it,

I'm on the new ha-guide now...

Builds locally, let's see whether Jenkins is happy:
https://review.openstack.org/122763

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Fri Sep 19 15:16:31 2014
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 19 Sep 2014 17:16:31 +0200
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <CAD0KtVH_gP1rhV-UvkZOrHcJwNHgDN3Qhe7sNOCoqSx8ZsDQJQ@mail.gmail.com>
References: <541C38C5.40808@suse.com>
 <CAD0KtVH_gP1rhV-UvkZOrHcJwNHgDN3Qhe7sNOCoqSx8ZsDQJQ@mail.gmail.com>
Message-ID: <541C48CF.6070509@suse.com>

On 09/19/2014 04:13 PM, Anne Gentle wrote:
> I'll do the removal patch from openstack-manuals. 

Great, thanks!

> I'm not completely sure how to set up ACL, so I would need help. I'll
> start the patch that removes, though.

It's setup now thanks to fungi, you just need to add more people to it.;)

Andreas

> On Fri, Sep 19, 2014 at 9:08 AM, Andreas Jaeger <aj at suse.com
> <mailto:aj at suse.com>> wrote:
> 
>     The new ha-guide repository is setup, you can clone it now.
> 
>     The ACLs need setup and I expect we need an initial patch to get
>     everything working as it should. I'll try to do this tonight but if
>     anybody else wants to start directly, speak up here and go for it,
> 
>     Andreas
>     --
>      Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org
>     <http://opensuse.org>} Twitter/Identica: jaegerandi
>       SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>        GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>         GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> 
>     _______________________________________________
>     Openstack-docs mailing list
>     Openstack-docs at lists.openstack.org
>     <mailto:Openstack-docs at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
> 


-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From berendt at b1-systems.de  Sat Sep 20 07:35:55 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Sat, 20 Sep 2014 09:35:55 +0200
Subject: [Openstack-docs] Move our conventions into one of our repositories
Message-ID: <541D2E5B.5020804@b1-systems.de>

Does it make sense to move our conventions from the wiki into one of our
repositories? This way we could publish the conventions on
docs.openstack.org.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From aj at suse.com  Sat Sep 20 10:23:17 2014
From: aj at suse.com (Andreas Jaeger)
Date: Sat, 20 Sep 2014 12:23:17 +0200
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <541C38C5.40808@suse.com>
References: <541C38C5.40808@suse.com>
Message-ID: <541D5595.70002@suse.com>

Everything should be setup in the repos, the gates pass, the guide gets
published etc.

Please double check and speak up if anything needs to be changed.

Andreas

P.S. The build jobs run quite often in timeouts reaching the java
repositories ;(

-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From mkassawara at gmail.com  Sat Sep 20 13:32:46 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Sat, 20 Sep 2014 08:32:46 -0500
Subject: [Openstack-docs] Move our conventions into one of our
	repositories
In-Reply-To: <541D2E5B.5020804@b1-systems.de>
References: <541D2E5B.5020804@b1-systems.de>
Message-ID: <CABA+jQpi4ZH3BpOiG6iyr7vWw94TQb74T5tBH4i7h=+veqw=bw@mail.gmail.com>

I think we discussed building a book at the last summit and decided to
stick with the wiki.

On Sat, Sep 20, 2014 at 2:35 AM, Christian Berendt <berendt at b1-systems.de>
wrote:

> Does it make sense to move our conventions from the wiki into one of our
> repositories? This way we could publish the conventions on
> docs.openstack.org.
>
> Christian.
>
> --
> Christian Berendt
> Cloud Solution Architect
> Mail: berendt at b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140920/3d3547bd/attachment.html>

From berendt at b1-systems.de  Sat Sep 20 16:01:53 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Sat, 20 Sep 2014 18:01:53 +0200
Subject: [Openstack-docs] Move of OpenStack Resource Agents
Message-ID: <541DA4F1.6010909@b1-systems.de>

At the moment the OpenStack Resource Agents used in the High
Availability Guide live in the repository madkiss/openstack-resource-agents.

I want to propose that we move them to Stackforge to be able to use the
common development workflows like Gerrit. Because the mentioned resource
agents are used in a official OpenStack document it is maybe even better
to move them into an official repository. Not sure if it is possible to
create and use a repository there, for example openstack/resource-agents.

Also I looks like the repository need a generic review. Most of the
files are 2 years old.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From anne at openstack.org  Sat Sep 20 17:59:01 2014
From: anne at openstack.org (Anne Gentle)
Date: Sat, 20 Sep 2014 12:59:01 -0500
Subject: [Openstack-docs] Move our conventions into one of our
	repositories
In-Reply-To: <CABA+jQpi4ZH3BpOiG6iyr7vWw94TQb74T5tBH4i7h=+veqw=bw@mail.gmail.com>
References: <541D2E5B.5020804@b1-systems.de>
 <CABA+jQpi4ZH3BpOiG6iyr7vWw94TQb74T5tBH4i7h=+veqw=bw@mail.gmail.com>
Message-ID: <CAD0KtVFFS6Y=bSQQ-_eZ3sWq0rWNf6otOLPRwfsZiheZ+aoj=Q@mail.gmail.com>

On Sat, Sep 20, 2014 at 8:32 AM, Matt Kassawara <mkassawara at gmail.com>
wrote:

> I think we discussed building a book at the last summit and decided to
> stick with the wiki.
>
>
Yep, that's my recollection of it as well. We reorganized the wiki pages to
make more pages rather than one long listing. I think that's still fine,
but sounds like you find it tougher somehow?
Anne


> On Sat, Sep 20, 2014 at 2:35 AM, Christian Berendt <berendt at b1-systems.de>
> wrote:
>
>> Does it make sense to move our conventions from the wiki into one of our
>> repositories? This way we could publish the conventions on
>> docs.openstack.org.
>>
>> Christian.
>>
>> --
>> Christian Berendt
>> Cloud Solution Architect
>> Mail: berendt at b1-systems.de
>>
>> B1 Systems GmbH
>> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
>> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140920/80fc5c22/attachment.html>

From anne at openstack.org  Sat Sep 20 18:01:32 2014
From: anne at openstack.org (Anne Gentle)
Date: Sat, 20 Sep 2014 13:01:32 -0500
Subject: [Openstack-docs] Move of OpenStack Resource Agents
In-Reply-To: <541DA4F1.6010909@b1-systems.de>
References: <541DA4F1.6010909@b1-systems.de>
Message-ID: <CAD0KtVG_=1K+sUg=h-4bq38E2SG_RQq=ioG-6k3r_Q_DUQuSUw@mail.gmail.com>

On Sat, Sep 20, 2014 at 11:01 AM, Christian Berendt <berendt at b1-systems.de>
wrote:

> At the moment the OpenStack Resource Agents used in the High
> Availability Guide live in the repository
> madkiss/openstack-resource-agents.
>
> I want to propose that we move them to Stackforge to be able to use the
> common development workflows like Gerrit. Because the mentioned resource
> agents are used in a official OpenStack document it is maybe even better
> to move them into an official repository. Not sure if it is possible to
> create and use a repository there, for example openstack/resource-agents.
>
>
I fully support this. Thanks for thinking of it!


> Also I looks like the repository need a generic review. Most of the
> files are 2 years old.
>
> Christian.
>
> --
> Christian Berendt
> Cloud Solution Architect
> Mail: berendt at b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140920/ae51dea6/attachment.html>

From seanroberts66 at gmail.com  Mon Sep 22 06:33:50 2014
From: seanroberts66 at gmail.com (Sean Roberts)
Date: Sun, 21 Sep 2014 23:33:50 -0700
Subject: [Openstack-docs] [training-guides] incubation discussion
Message-ID: <B2741144-9F2D-46AD-AE24-AC93501AAF34@gmail.com>

We started discussing incubating the training guides project a while ago. It seemed that there was enough differences to consider the project separate from the other docs projects. We had a new repository created as a first step in this direction. Due to the current publishing of the training guides to docs.openstack.org, we collectively decided to create the new repo in the OpenStack github organization. 
Fast forward to the current time. Between the neutron and nova projects, they are both debating spinning off sub-projects. These would have some incubation properties and goals. 
I recommend we wait for these incubation sub-projects plans to play out over the next few months before we make a decision on the training guides incubation. 
Team, what do you think?

~sean

From anne at openstack.org  Mon Sep 22 14:56:29 2014
From: anne at openstack.org (Anne Gentle)
Date: Mon, 22 Sep 2014 09:56:29 -0500
Subject: [Openstack-docs] Move Doc Team meeting to Thursday 1400 UTC *just
	this week*
Message-ID: <CAD0KtVGSpkmN2+z3-EkLopm5QOs4j1wi+5sPKK1-ODZvQs90mQ@mail.gmail.com>

Hi all,
I've updated the wiki page at
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
with a new agenda and to set the time for Thursday Sep 22, 2014, 1400 UTC
in #openstack-meeting. I'm at an internal conference (for docs, imagine!)
Tuesday and Wed. this week.

Please feel free to add items to the agenda on the wiki. I hope the day
offset works for most of us.
Thanks,
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/50edb815/attachment.html>

From nchase at mirantis.com  Mon Sep 22 15:04:37 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Mon, 22 Sep 2014 11:04:37 -0400
Subject: [Openstack-docs] Move Doc Team meeting to Thursday 1400 UTC
 *just this week*
In-Reply-To: <CAD0KtVGSpkmN2+z3-EkLopm5QOs4j1wi+5sPKK1-ODZvQs90mQ@mail.gmail.com>
References: <CAD0KtVGSpkmN2+z3-EkLopm5QOs4j1wi+5sPKK1-ODZvQs90mQ@mail.gmail.com>
Message-ID: <54203A85.3000202@mirantis.com>

works for me.

On 9/22/2014 10:56 AM, Anne Gentle wrote:
> Hi all,
> I've updated the wiki page at 
> https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting 
> with a new agenda and to set the time for Thursday Sep 22, 2014, 1400 
> UTC in #openstack-meeting. I'm at an internal conference (for docs, 
> imagine!) Tuesday and Wed. this week.
>
> Please feel free to add items to the agenda on the wiki. I hope the 
> day offset works for most of us.
> Thanks,
> Anne
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
<http://openstacksv.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/aa137d51/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: www.openstacksv.com_.png
Type: image/png
Size: 7160 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/aa137d51/attachment.png>

From anne at openstack.org  Mon Sep 22 15:11:22 2014
From: anne at openstack.org (Anne Gentle)
Date: Mon, 22 Sep 2014 10:11:22 -0500
Subject: [Openstack-docs] Move Doc Team meeting to Thursday 1400 UTC
	*just this week*
In-Reply-To: <CAD0KtVGSpkmN2+z3-EkLopm5QOs4j1wi+5sPKK1-ODZvQs90mQ@mail.gmail.com>
References: <CAD0KtVGSpkmN2+z3-EkLopm5QOs4j1wi+5sPKK1-ODZvQs90mQ@mail.gmail.com>
Message-ID: <CAD0KtVGAdS9oXXFi8Vmnn12mN-fVtW-1Y15e6+nSn3N7gZLnvg@mail.gmail.com>

Oh and I realized that we'll need to be in #openstack-meeting-3. I've
updated the wiki page to reflect the meeting room change.

On Mon, Sep 22, 2014 at 9:56 AM, Anne Gentle <anne at openstack.org> wrote:

> Hi all,
> I've updated the wiki page at
> https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting
> with a new agenda and to set the time for Thursday Sep 22, 2014, 1400 UTC
> in #openstack-meeting. I'm at an internal conference (for docs, imagine!)
> Tuesday and Wed. this week.
>
> Please feel free to add items to the agenda on the wiki. I hope the day
> offset works for most of us.
> Thanks,
> Anne
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/dd346971/attachment.html>

From anne at openstack.org  Mon Sep 22 16:50:01 2014
From: anne at openstack.org (Anne Gentle)
Date: Mon, 22 Sep 2014 11:50:01 -0500
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <541D5595.70002@suse.com>
References: <541C38C5.40808@suse.com> <541D5595.70002@suse.com>
Message-ID: <CAD0KtVFsj34vzUUHGxeN06aP5QpNVD9VEM=eEcD7MPGb-ywasg@mail.gmail.com>

Thanks again for all this work!

The repo is at http://git.openstack.org/cgit/openstack/ha-guide/

The core reviewer team for the HA guide consists of these four:
David Medberry
Emilien Macchi
Matt Griffin
Sriram Subramanian

The docs-core team is an included group so we also have +2 ability on the
repository also.

The Security team has a specific set of rules for their guide, where at
least two of the security team members must review a patch. Would you like
something similar for the HA Guide, or is two +2 votes sufficient to get
you all bootstrapped and get going?

Thanks,
Anne


On Sat, Sep 20, 2014 at 5:23 AM, Andreas Jaeger <aj at suse.com> wrote:

> Everything should be setup in the repos, the gates pass, the guide gets
> published etc.
>
> Please double check and speak up if anything needs to be changed.
>
> Andreas
>
> P.S. The build jobs run quite often in timeouts reaching the java
> repositories ;(
>
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/65c54057/attachment-0001.html>

From anne at openstack.org  Mon Sep 22 16:53:51 2014
From: anne at openstack.org (Anne Gentle)
Date: Mon, 22 Sep 2014 11:53:51 -0500
Subject: [Openstack-docs] [training-guides] incubation discussion
In-Reply-To: <B2741144-9F2D-46AD-AE24-AC93501AAF34@gmail.com>
References: <B2741144-9F2D-46AD-AE24-AC93501AAF34@gmail.com>
Message-ID: <CAD0KtVGPzhq3=2i7ZWnRH5_X5r8xuEVFf8b1LNtrFUghm4WX6g@mail.gmail.com>

I'm double-booked at your meeting time today, so I thought I'd write a
response here.

On Mon, Sep 22, 2014 at 1:33 AM, Sean Roberts <seanroberts66 at gmail.com>
wrote:

> We started discussing incubating the training guides project a while ago.
> It seemed that there was enough differences to consider the project
> separate from the other docs projects. We had a new repository created as a
> first step in this direction. Due to the current publishing of the training
> guides to docs.openstack.org, we collectively decided to create the new
> repo in the OpenStack github organization.
> Fast forward to the current time. Between the neutron and nova projects,
> they are both debating spinning off sub-projects. These would have some
> incubation properties and goals.
> I recommend we wait for these incubation sub-projects plans to play out
> over the next few months before we make a decision on the training guides
> incubation.
>

I know you're not asking me, and you're asking the team, which is cool. But
I need to point out that your comparison may not be apt here. The neutron
incubation discussion is about merging features or entire APIs into the
neutron tree. I don't think that's your end goal here, your end goal sounds
like standing up a new program just for training due to the differences
from docs.

Just not sure the neutron incubation path discussion is a match for this
discussion, they're a bit too different for me to wrap my head around the
comparison.

Do you want a separate team and PTL? What benefits are you seeking?

That's more of the discussion than looking for an existing pattern, I
think. Let me know what your goals are.

Thanks,
Anne


> Team, what do you think?
>
> ~sean
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/e70ff299/attachment.html>

From seanroberts66 at gmail.com  Mon Sep 22 17:03:56 2014
From: seanroberts66 at gmail.com (Sean Roberts)
Date: Mon, 22 Sep 2014 10:03:56 -0700
Subject: [Openstack-docs] [training-guides] incubation discussion
In-Reply-To: <CAD0KtVGPzhq3=2i7ZWnRH5_X5r8xuEVFf8b1LNtrFUghm4WX6g@mail.gmail.com>
References: <B2741144-9F2D-46AD-AE24-AC93501AAF34@gmail.com>
 <CAD0KtVGPzhq3=2i7ZWnRH5_X5r8xuEVFf8b1LNtrFUghm4WX6g@mail.gmail.com>
Message-ID: <23CC4FA5-0653-47B9-8351-D23B19A83C91@gmail.com>

These are definitely different groups with different purposes, but they are seeking to give a smaller group some self rule while coordinating their  goals with the larger group. The incubation benefits are PTL elections, recognition of being an established group, and inclusion in the OpenStack github org. Did I miss anything? 

~sean

> On Sep 22, 2014, at 9:53 AM, Anne Gentle <anne at openstack.org> wrote:
> 
> I'm double-booked at your meeting time today, so I thought I'd write a response here.
> 
>> On Mon, Sep 22, 2014 at 1:33 AM, Sean Roberts <seanroberts66 at gmail.com> wrote:
>> We started discussing incubating the training guides project a while ago. It seemed that there was enough differences to consider the project separate from the other docs projects. We had a new repository created as a first step in this direction. Due to the current publishing of the training guides to docs.openstack.org, we collectively decided to create the new repo in the OpenStack github organization.
>> Fast forward to the current time. Between the neutron and nova projects, they are both debating spinning off sub-projects. These would have some incubation properties and goals.
>> I recommend we wait for these incubation sub-projects plans to play out over the next few months before we make a decision on the training guides incubation.
> 
> I know you're not asking me, and you're asking the team, which is cool. But I need to point out that your comparison may not be apt here. The neutron incubation discussion is about merging features or entire APIs into the neutron tree. I don't think that's your end goal here, your end goal sounds like standing up a new program just for training due to the differences from docs. 
> 
> Just not sure the neutron incubation path discussion is a match for this discussion, they're a bit too different for me to wrap my head around the comparison. 
> 
> Do you want a separate team and PTL? What benefits are you seeking? 
> 
> That's more of the discussion than looking for an existing pattern, I think. Let me know what your goals are. 
> 
> Thanks,
> Anne 
>  
>> Team, what do you think?
>> 
>> ~sean
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/7f138969/attachment.html>

From seanroberts66 at gmail.com  Mon Sep 22 17:07:37 2014
From: seanroberts66 at gmail.com (Sean Roberts)
Date: Mon, 22 Sep 2014 10:07:37 -0700
Subject: [Openstack-docs] [training-guides] incubation discussion
In-Reply-To: <CAD0KtVGPzhq3=2i7ZWnRH5_X5r8xuEVFf8b1LNtrFUghm4WX6g@mail.gmail.com>
References: <B2741144-9F2D-46AD-AE24-AC93501AAF34@gmail.com>
 <CAD0KtVGPzhq3=2i7ZWnRH5_X5r8xuEVFf8b1LNtrFUghm4WX6g@mail.gmail.com>
Message-ID: <BD949BB5-F21C-482B-9380-913D4C071B97@gmail.com>

Ah as far as goals, I'm looking for greater adoption, participation, and keeping up with the releases. The recognition of incubation would help with that. 

~sean

> On Sep 22, 2014, at 9:53 AM, Anne Gentle <anne at openstack.org> wrote:
> 
> I'm double-booked at your meeting time today, so I thought I'd write a response here.
> 
>> On Mon, Sep 22, 2014 at 1:33 AM, Sean Roberts <seanroberts66 at gmail.com> wrote:
>> We started discussing incubating the training guides project a while ago. It seemed that there was enough differences to consider the project separate from the other docs projects. We had a new repository created as a first step in this direction. Due to the current publishing of the training guides to docs.openstack.org, we collectively decided to create the new repo in the OpenStack github organization.
>> Fast forward to the current time. Between the neutron and nova projects, they are both debating spinning off sub-projects. These would have some incubation properties and goals.
>> I recommend we wait for these incubation sub-projects plans to play out over the next few months before we make a decision on the training guides incubation.
> 
> I know you're not asking me, and you're asking the team, which is cool. But I need to point out that your comparison may not be apt here. The neutron incubation discussion is about merging features or entire APIs into the neutron tree. I don't think that's your end goal here, your end goal sounds like standing up a new program just for training due to the differences from docs. 
> 
> Just not sure the neutron incubation path discussion is a match for this discussion, they're a bit too different for me to wrap my head around the comparison. 
> 
> Do you want a separate team and PTL? What benefits are you seeking? 
> 
> That's more of the discussion than looking for an existing pattern, I think. Let me know what your goals are. 
> 
> Thanks,
> Anne 
>  
>> Team, what do you think?
>> 
>> ~sean
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/7e597190/attachment.html>

From aj at suse.com  Mon Sep 22 17:43:36 2014
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 22 Sep 2014 19:43:36 +0200
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <CAD0KtVFsj34vzUUHGxeN06aP5QpNVD9VEM=eEcD7MPGb-ywasg@mail.gmail.com>
References: <541C38C5.40808@suse.com> <541D5595.70002@suse.com>
 <CAD0KtVFsj34vzUUHGxeN06aP5QpNVD9VEM=eEcD7MPGb-ywasg@mail.gmail.com>
Message-ID: <54205FC8.3030905@suse.com>

On 09/22/2014 06:50 PM, Anne Gentle wrote:
> Thanks again for all this work!
> 
> The repo is at http://git.openstack.org/cgit/openstack/ha-guide/
> 
> The core reviewer team for the HA guide consists of these four:
> David Medberry
> Emilien Macchi
> Matt Griffin
> Sriram Subramanian
> 
> The docs-core team is an included group so we also have +2 ability on
> the repository also.
> 
> The Security team has a specific set of rules for their guide, where at
> least two of the security team members must review a patch. Would you

The rule is: One +2 from security team, one from documentation team.

> like something similar for the HA Guide, or is two +2 votes sufficient
> to get you all bootstrapped and get going?

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From sriram at sriramhere.com  Mon Sep 22 18:21:34 2014
From: sriram at sriramhere.com (Sriram Subramanian)
Date: Mon, 22 Sep 2014 11:21:34 -0700
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <54205FC8.3030905@suse.com>
References: <541C38C5.40808@suse.com> <541D5595.70002@suse.com>
 <CAD0KtVFsj34vzUUHGxeN06aP5QpNVD9VEM=eEcD7MPGb-ywasg@mail.gmail.com>
 <54205FC8.3030905@suse.com>
Message-ID: <CAP6wb7+6thHtDgpkLfJ+E+Qkcd=+PY-GYvJcdue3nKXm9WArEw@mail.gmail.com>

Thanks Anne for setting this up.

+1 on The rule is: One +2 from security team, one from documentation team.

Also, can someone list open bugs related to ha-guide? If there is no tag
yet, I'd like to add a new tag for these bugs: "ha-guide"

On Mon, Sep 22, 2014 at 10:43 AM, Andreas Jaeger <aj at suse.com> wrote:

> On 09/22/2014 06:50 PM, Anne Gentle wrote:
> > Thanks again for all this work!
> >
> > The repo is at http://git.openstack.org/cgit/openstack/ha-guide/
> >
> > The core reviewer team for the HA guide consists of these four:
> > David Medberry
> > Emilien Macchi
> > Matt Griffin
> > Sriram Subramanian
> >
> > The docs-core team is an included group so we also have +2 ability on
> > the repository also.
> >
> > The Security team has a specific set of rules for their guide, where at
> > least two of the security team members must review a patch. Would you
>
> The rule is: One +2 from security team, one from documentation team.
>
> > like something similar for the HA Guide, or is two +2 votes sufficient
> > to get you all bootstrapped and get going?
>
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Thanks,
-Sriram
425-610-8465
www.sriramhere.com | www.clouddon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/3dff8d75/attachment-0001.html>

From aj at suse.com  Mon Sep 22 18:45:59 2014
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 22 Sep 2014 20:45:59 +0200
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <CAP6wb7+6thHtDgpkLfJ+E+Qkcd=+PY-GYvJcdue3nKXm9WArEw@mail.gmail.com>
References: <541C38C5.40808@suse.com>	<541D5595.70002@suse.com>	<CAD0KtVFsj34vzUUHGxeN06aP5QpNVD9VEM=eEcD7MPGb-ywasg@mail.gmail.com>	<54205FC8.3030905@suse.com>
 <CAP6wb7+6thHtDgpkLfJ+E+Qkcd=+PY-GYvJcdue3nKXm9WArEw@mail.gmail.com>
Message-ID: <54206E67.9010004@suse.com>

On 09/22/2014 08:21 PM, Sriram Subramanian wrote:
> Thanks Anne for setting this up.
> 
> +1 on The rule is: One +2 from security team, one from documentation team.

You mean: one +2 from ha team, one from docu team?

> Also, can someone list open bugs related to ha-guide? If there is no tag
> yet, I'd like to add a new tag for these bugs: "ha-guide"

Currently 3 open bugs are tagged:
https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=ha-guide

But let's check the full list and see whether we missed a bug...

Andreas

> On Mon, Sep 22, 2014 at 10:43 AM, Andreas Jaeger <aj at suse.com
> <mailto:aj at suse.com>> wrote:
> 
>     On 09/22/2014 06:50 PM, Anne Gentle wrote:
>     > Thanks again for all this work!
>     >
>     > The repo is at http://git.openstack.org/cgit/openstack/ha-guide/
>     >
>     > The core reviewer team for the HA guide consists of these four:
>     > David Medberry
>     > Emilien Macchi
>     > Matt Griffin
>     > Sriram Subramanian
>     >
>     > The docs-core team is an included group so we also have +2 ability on
>     > the repository also.
>     >
>     > The Security team has a specific set of rules for their guide, where at
>     > least two of the security team members must review a patch. Would you
> 
>     The rule is: One +2 from security team, one from documentation team.
> 
>     > like something similar for the HA Guide, or is two +2 votes sufficient
>     > to get you all bootstrapped and get going?
> 
>     Andreas
>     --
>      Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org
>     <http://opensuse.org>} Twitter/Identica: jaegerandi
>       SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>        GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>         GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> 
>     _______________________________________________
>     Openstack-docs mailing list
>     Openstack-docs at lists.openstack.org
>     <mailto:Openstack-docs at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
> 
> 
> 
> -- 
> Thanks,
> -Sriram 
> 425-610-8465
> www.sriramhere.com <http://www.sriramhere.com> | www.clouddon.com
> <http://www.clouddon.com>


-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From berendt at b1-systems.de  Mon Sep 22 19:07:03 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Mon, 22 Sep 2014 21:07:03 +0200
Subject: [Openstack-docs] Move Doc Team meeting to Thursday 1400 UTC
 *just this week*
In-Reply-To: <CAD0KtVGSpkmN2+z3-EkLopm5QOs4j1wi+5sPKK1-ODZvQs90mQ@mail.gmail.com>
References: <CAD0KtVGSpkmN2+z3-EkLopm5QOs4j1wi+5sPKK1-ODZvQs90mQ@mail.gmail.com>
Message-ID: <54207357.1070102@b1-systems.de>

On 09/22/2014 04:56 PM, Anne Gentle wrote:
> Please feel free to add items to the agenda on the wiki.

I added the move of the resource agents to the agenda.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From sriram at sriramhere.com  Mon Sep 22 19:31:17 2014
From: sriram at sriramhere.com (Sriram Subramanian)
Date: Mon, 22 Sep 2014 12:31:17 -0700
Subject: [Openstack-docs] new ha-guide is setup
In-Reply-To: <54206E67.9010004@suse.com>
References: <541C38C5.40808@suse.com> <541D5595.70002@suse.com>
 <CAD0KtVFsj34vzUUHGxeN06aP5QpNVD9VEM=eEcD7MPGb-ywasg@mail.gmail.com>
 <54205FC8.3030905@suse.com>
 <CAP6wb7+6thHtDgpkLfJ+E+Qkcd=+PY-GYvJcdue3nKXm9WArEw@mail.gmail.com>
 <54206E67.9010004@suse.com>
Message-ID: <CAP6wb7KMvB9afNet3ST73rxRWhJgB1p++LSnQwrU8E5rXC+fcQ@mail.gmail.com>

yes :) thanks!

On Mon, Sep 22, 2014 at 11:45 AM, Andreas Jaeger <aj at suse.com> wrote:

> On 09/22/2014 08:21 PM, Sriram Subramanian wrote:
> > Thanks Anne for setting this up.
> >
> > +1 on The rule is: One +2 from security team, one from documentation
> team.
>
> You mean: one +2 from ha team, one from docu team?
>
> > Also, can someone list open bugs related to ha-guide? If there is no tag
> > yet, I'd like to add a new tag for these bugs: "ha-guide"
>
> Currently 3 open bugs are tagged:
> https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=ha-guide
>
> But let's check the full list and see whether we missed a bug...
>
> Andreas
>
> > On Mon, Sep 22, 2014 at 10:43 AM, Andreas Jaeger <aj at suse.com
> > <mailto:aj at suse.com>> wrote:
> >
> >     On 09/22/2014 06:50 PM, Anne Gentle wrote:
> >     > Thanks again for all this work!
> >     >
> >     > The repo is at http://git.openstack.org/cgit/openstack/ha-guide/
> >     >
> >     > The core reviewer team for the HA guide consists of these four:
> >     > David Medberry
> >     > Emilien Macchi
> >     > Matt Griffin
> >     > Sriram Subramanian
> >     >
> >     > The docs-core team is an included group so we also have +2 ability
> on
> >     > the repository also.
> >     >
> >     > The Security team has a specific set of rules for their guide,
> where at
> >     > least two of the security team members must review a patch. Would
> you
> >
> >     The rule is: One +2 from security team, one from documentation team.
> >
> >     > like something similar for the HA Guide, or is two +2 votes
> sufficient
> >     > to get you all bootstrapped and get going?
> >
> >     Andreas
> >     --
> >      Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org
> >     <http://opensuse.org>} Twitter/Identica: jaegerandi
> >       SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
> >        GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG
> N?rnberg)
> >         GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272
> A126
> >
> >     _______________________________________________
> >     Openstack-docs mailing list
> >     Openstack-docs at lists.openstack.org
> >     <mailto:Openstack-docs at lists.openstack.org>
> >     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> >
> >
> >
> >
> > --
> > Thanks,
> > -Sriram
> > 425-610-8465
> > www.sriramhere.com <http://www.sriramhere.com> | www.clouddon.com
> > <http://www.clouddon.com>
>
>
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
>



-- 
Thanks,
-Sriram
425-610-8465
www.sriramhere.com | www.clouddon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140922/6c679a22/attachment.html>

From tomo at dream.daynight.jp  Tue Sep 23 06:44:49 2014
From: tomo at dream.daynight.jp (KATO Tomoyuki)
Date: Tue, 23 Sep 2014 15:44:49 +0900
Subject: [Openstack-docs] [TG] reference to old training guides
In-Reply-To: <CAD0KtVGBY0D1Xe6XYeSEJ_V-nNrN5iHvzgbn+Vvz_3tvqdQR=g@mail.gmail.com>
References: <CAD0KtVGoo9anMgxgdDQvBZgVO6gvc5CwcrGvGYCNhse_0Gd6zw@mail.gmail.com>
 <CAD0KtVGBY0D1Xe6XYeSEJ_V-nNrN5iHvzgbn+Vvz_3tvqdQR=g@mail.gmail.com>
Message-ID: <201409230644.s8N6inX1042187@www2826.sakura.ne.jp>

> More comments on the bug itself, but thought I'd also bring it up here for
> more eyes. I deleted the file mentioned in the bug. However there are many
> files with a Jan 31 2014 date like this one, should they all be deleted?
> 
> There are many other files with a Jul 21 2014 date, should those be deleted?
> 
> Thanks,
> Anne

I think we should delete old files.
Redirect the old urls to new contents as necessary.

thought? > training guide team

--
KATO Tomoyuki


From frans at meruvian.org  Wed Sep 24 14:40:58 2014
From: frans at meruvian.org (Frans Thamura)
Date: Wed, 24 Sep 2014 21:40:58 +0700
Subject: [Openstack-docs] managing translation
Message-ID: <CAOeeQyrXLCeS6Z3bu27goajqMVEtyadbGk2k5Sf7tc_R_rkN1A@mail.gmail.com>

hi all

our team has now translating in the transifex


any idea to manage the work?

my role coordinator for indonesian translation


and yes, more more word counting :)

6 collaborator right now

one reviewer

tips plz

F


From vvaldez at redhat.com  Wed Sep 24 18:22:15 2014
From: vvaldez at redhat.com (Vinny Valdez)
Date: Wed, 24 Sep 2014 13:22:15 -0500
Subject: [Openstack-docs] Architecture Design Guide image SVG format.
In-Reply-To: <337812101.22091710.1406287969780.JavaMail.zimbra@redhat.com>
References: <1040360932.21912369.1406248696208.JavaMail.zimbra@redhat.com>
 <F45002AE-D43C-4C87-854F-14A2F00AE90B@redhat.com>
 <337812101.22091710.1406287969780.JavaMail.zimbra@redhat.com>
Message-ID: <E35B870B-4940-4520-BD53-0AB1EF95A95F@redhat.com>

Hopefully better late than never:  https://review.openstack.org/123807

I exported all the images to SVG, but all the icons were exported as supporting PDF files which is messy. The SVG would only open properly in Safari, not Chrome or Firefox. I can put everything into arch-design/images/SVG/ folder if that makes sense. For now I only uploaded the source OmniGraffle file I created these in. Let me know what I can do to make this more accessible by all.

Vinny Valdez, RHCA, RHCSS, RHCVA (110-119-187)
Principal Enterprise Architect
Cloud Practice
+1 (512) 718-5572

On Jul 25, 2014, at 6:32 AM, Steve Gordon <sgordon at redhat.com> wrote:

> ----- Original Message -----
>> From: "Vinny Valdez" <vvaldez at redhat.com>
>> To: "Steve Gordon" <sgordon at redhat.com>
>> 
>> Hi Steve, yes I have the source files and I'm happy to upload them. Where is
>> the repo I can commit them to?
>> 
>> Vinny
> 
> Hi Vinny,
> 
> They ultimately need to end up here:
> 
>    http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/arch-design/images
> 
> In the event that you haven't committed to the openstack-manuals repository before instructions can be found here:
> 
>    https://wiki.openstack.org/wiki/Documentation/HowTo#Edit_OpenStack_RST_and.2For_DocBook_documentation
> 
> Thanks!
> 
> Steve
> 
>> On Jul 25, 2014, at 2:38 AM, Steve Gordon <sgordon at redhat.com> wrote:
>> 
>>> Hi Vinny,
>>> 
>>> Do you still have SVG format files for the images you created for the
>>> architecture design guide? Would it be possible for you to upload them
>>> somewhere so that we can get them into git? Apologies if someone has
>>> already followed up on this :).
>>> 
>>> Thanks,
>>> 
>>> Steve
>> 
>> 
> 
> -- 
> Steve Gordon, RHCE
> Sr. Technical Product Manager,
> Red Hat Enterprise Linux OpenStack Platform

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140924/0e8bb7a4/attachment.html>

From aj at suse.com  Wed Sep 24 18:53:04 2014
From: aj at suse.com (Andreas Jaeger)
Date: Wed, 24 Sep 2014 20:53:04 +0200
Subject: [Openstack-docs] managing translation
In-Reply-To: <CAOeeQyrXLCeS6Z3bu27goajqMVEtyadbGk2k5Sf7tc_R_rkN1A@mail.gmail.com>
References: <CAOeeQyrXLCeS6Z3bu27goajqMVEtyadbGk2k5Sf7tc_R_rkN1A@mail.gmail.com>
Message-ID: <54231310.3090408@suse.com>

On 09/24/2014 04:40 PM, Frans Thamura wrote:
> hi all
> 
> our team has now translating in the transifex
> 
> 
> any idea to manage the work?
> 
> my role coordinator for indonesian translation
> 
> 
> and yes, more more word counting :)
> 
> 6 collaborator right now
> 
> one reviewer
> 
> tips plz

Frans, there's an openstack-i18n mailing list, could you ask there, please?

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From tom at openstack.org  Thu Sep 25 01:47:09 2014
From: tom at openstack.org (Tom Fifield)
Date: Thu, 25 Sep 2014 09:47:09 +0800
Subject: [Openstack-docs] managing translation
In-Reply-To: <CAOeeQyrXLCeS6Z3bu27goajqMVEtyadbGk2k5Sf7tc_R_rkN1A@mail.gmail.com>
References: <CAOeeQyrXLCeS6Z3bu27goajqMVEtyadbGk2k5Sf7tc_R_rkN1A@mail.gmail.com>
Message-ID: <5423741D.9060401@openstack.org>

Perhaps ask on the openstack-i18n list ?

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n



On 24/09/14 22:40, Frans Thamura wrote:
> hi all
> 
> our team has now translating in the transifex
> 
> 
> any idea to manage the work?
> 
> my role coordinator for indonesian translation
> 
> 
> and yes, more more word counting :)
> 
> 6 collaborator right now
> 
> one reviewer
> 
> tips plz
> 
> F
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 



From nchase at mirantis.com  Thu Sep 25 13:56:45 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Thu, 25 Sep 2014 09:56:45 -0400
Subject: [Openstack-docs] Welcome to Elke Vorheis!
Message-ID: <54241F1D.7070402@mirantis.com>

Just wanted to take a moment to welcome Elke Vorheis, an experienced 
contract technical writer who's going to be helping us out in getting 
through our backlog.  Elke will start out helping with the Networking 
Guide and the Install Guide where needed.

Thanks, and welcome aboard, Elke!

----  Nick
-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now


From elkev at yahoo.com  Thu Sep 25 14:01:22 2014
From: elkev at yahoo.com (Elke Vorheis)
Date: Thu, 25 Sep 2014 07:01:22 -0700
Subject: [Openstack-docs] Welcome to Elke Vorheis!
In-Reply-To: <54241F1D.7070402@mirantis.com>
References: <54241F1D.7070402@mirantis.com>
Message-ID: <1411653682.77274.YahooMailNeo@web126103.mail.ne1.yahoo.com>

Thanks for the welcoming words. Elke
 
Elke Vorheis
(650) 291-1375 (cell)
elkev at yahoo.com (email)


On Thursday, September 25, 2014 6:58 AM, Nicholas Chase <nchase at mirantis.com> wrote:
 


Just wanted to take a moment to welcome Elke Vorheis, an experienced 
contract technical writer who's going to be helping us out in getting 
through our backlog.  Elke will start out helping with the Networking 
Guide and the Install Guide where needed.

Thanks, and welcome aboard, Elke!

----  Nick
-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140925/6ae9640e/attachment.html>

From anne at openstack.org  Thu Sep 25 20:22:24 2014
From: anne at openstack.org (Anne Gentle)
Date: Thu, 25 Sep 2014 15:22:24 -0500
Subject: [Openstack-docs] Welcome to Elke Vorheis!
In-Reply-To: <54241F1D.7070402@mirantis.com>
References: <54241F1D.7070402@mirantis.com>
Message-ID: <CAD0KtVFbc3dw8B4nxce5BG9j-hDvkMrFAW7xMtU1+qG9OYaRtA@mail.gmail.com>

Welcome Elke! So nice to have you here. Feel free to ask us questions here,
on IRC, or you can call/Skype me. I'm annegentle all over the place. :)

Thanks for working with us!
Anne

On Thu, Sep 25, 2014 at 8:56 AM, Nicholas Chase <nchase at mirantis.com> wrote:

> Just wanted to take a moment to welcome Elke Vorheis, an experienced
> contract technical writer who's going to be helping us out in getting
> through our backlog.  Elke will start out helping with the Networking Guide
> and the Install Guide where needed.
>
> Thanks, and welcome aboard, Elke!
>
> ----  Nick
> --
> Nick Chase
> 1-650-567-5640
> Technical Marketing Manager, Mirantis
> Editor, OpenStack:Now
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140925/e6d2f3ed/attachment.html>

From elkev at yahoo.com  Thu Sep 25 20:40:30 2014
From: elkev at yahoo.com (Elke Vorheis)
Date: Thu, 25 Sep 2014 13:40:30 -0700
Subject: [Openstack-docs] Welcome to Elke Vorheis!
In-Reply-To: <CAD0KtVFbc3dw8B4nxce5BG9j-hDvkMrFAW7xMtU1+qG9OYaRtA@mail.gmail.com>
References: <54241F1D.7070402@mirantis.com>
 <CAD0KtVFbc3dw8B4nxce5BG9j-hDvkMrFAW7xMtU1+qG9OYaRtA@mail.gmail.com>
Message-ID: <1411677630.71003.YahooMailNeo@web126105.mail.ne1.yahoo.com>

Hi Anne,

Thanks for the kind words. Looking forward to working with you. By the way, I sent an invite on Skype. Elke
 
Elke Vorheis
(650) 291-1375 (cell)
elkev at yahoo.com (email)


On Thursday, September 25, 2014 1:22 PM, Anne Gentle <anne at openstack.org> wrote:
 


Welcome Elke! So nice to have you here. Feel free to ask us questions here, on IRC, or you can call/Skype me. I'm annegentle all over the place. :)

Thanks for working with us!
Anne


On Thu, Sep 25, 2014 at 8:56 AM, Nicholas Chase <nchase at mirantis.com> wrote:

Just wanted to take a moment to welcome Elke Vorheis, an experienced contract technical writer who's going to be helping us out in getting through our backlog.  Elke will start out helping with the Networking Guide and the Install Guide where needed.
>
>Thanks, and welcome aboard, Elke!
>
>----  Nick
>-- 
>Nick Chase
>1-650-567-5640
>Technical Marketing Manager, Mirantis
>Editor, OpenStack:Now
>
>_______________________________________________
>Openstack-docs mailing list
>Openstack-docs at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140925/bfb95a96/attachment.html>

From tom at openstack.org  Fri Sep 26 06:41:08 2014
From: tom at openstack.org (Tom Fifield)
Date: Fri, 26 Sep 2014 14:41:08 +0800
Subject: [Openstack-docs] Juno Install Testing
Message-ID: <54250A84.1020508@openstack.org>

Hi all,

Finally found some time to do a bit of testing on Juno.

Using our Ubuntu 14.04 install guide with just one modification (using
the staging PPA, rather than the not-yet-ready cloud archive), with
milestone 3 packages, here's the good news:

* Keystone works
* Glance works
* Nova install with nova-network works

and the bad bits:
* ubuntu-cloud-archive:juno is not ready
* horizon does not work due to a dependency problem
(https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1374273)

So far haven't tested other projects, but at least for these the docs
look in good shape.

Tracking testing progress @
https://wiki.openstack.org/wiki/JunoDocTesting#Install_Guide - please
join in if you have time :)


Regards,


Tom


From baspeters93 at gmail.com  Fri Sep 26 07:54:51 2014
From: baspeters93 at gmail.com (Bas Peters)
Date: Fri, 26 Sep 2014 09:54:51 +0200
Subject: [Openstack-docs] Getting started
Message-ID: <001d01cfd95f$2804fdd0$780ef970$@gmail.com>

Hey everyone,

 

I'm new to the mailing list (and Openstack in general) and would like to
start contributing now that I have some more time on my hands. Problem is I
just rolled out of college and have never seriously contributed to an open
source project. What's the best way for me to get started? I saw an e-mail
come by about install-guide testing and logging bugs against any errors I
might find. I was wondering if there's some coordinating mechanism in place
so I can see what distribution I could best focus on?

 

With kind regards,

 

Bas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140926/8b39fa5e/attachment-0001.html>

From tom at openstack.org  Fri Sep 26 08:27:43 2014
From: tom at openstack.org (Tom Fifield)
Date: Fri, 26 Sep 2014 16:27:43 +0800
Subject: [Openstack-docs] Getting started
In-Reply-To: <001d01cfd95f$2804fdd0$780ef970$@gmail.com>
References: <001d01cfd95f$2804fdd0$780ef970$@gmail.com>
Message-ID: <5425237F.1060307@openstack.org>

On 26/09/14 15:54, Bas Peters wrote:
> Hey everyone,
> 
>  
> 
> I?m new to the mailing list (and Openstack in general) and would like to
> start contributing now that I have some more time on my hands. Problem
> is I just rolled out of college and have never seriously contributed to
> an open source project. What?s the best way for me to get started? I saw
> an e-mail come by about install-guide testing and logging bugs against
> any errors I might find. I was wondering if there?s some coordinating
> mechanism in place so I can see what distribution I could best focus on?
> 
>  
> 
> With kind regards,
> 
>  
> 
> Bas

Hi Bas,

Great to have you!

Indeed you're right - we're going to cut the next release of OpenStack
(Juno) on October 16th, and before then we want to test the installation
as much as possible.

If you've never installed OpenStack before, you're perfect for the job
and also, more generally looking through any OpenStack docs and just
lodging tonnes of bugs with anything that doesn't make sense or is
difficult to find.

There's three main mechanisms for coordination
1) this mailing list
2) the weekly documentation team IRC meeting
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
3) the matrix at
https://wiki.openstack.org/wiki/JunoDocTesting#Install_Guide

To participate in the install guide testing, you just need a couple of
machines (real or virtual), and you can follow your favourite install
guide at http://docs.openstack.org/trunk/ and update the matrix/lodge
bugs as appropriate.


We're here to help (and we need yours!), feel free to post any questions
on the mailing list, or heading into #openstack-doc on the freenode IRC
network to chat.

Thanks for supporting OpenStack.

Regards,


Tom



From berendt at b1-systems.de  Fri Sep 26 08:47:35 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Fri, 26 Sep 2014 10:47:35 +0200
Subject: [Openstack-docs] Getting started
In-Reply-To: <5425237F.1060307@openstack.org>
References: <001d01cfd95f$2804fdd0$780ef970$@gmail.com>
 <5425237F.1060307@openstack.org>
Message-ID: <54252827.2020402@b1-systems.de>

On 09/26/2014 10:27 AM, Tom Fifield wrote:
> To participate in the install guide testing, you just need a couple of
> machines (real or virtual), and you can follow your favourite install
> guide at http://docs.openstack.org/trunk/ and update the matrix/lodge
> bugs as appropriate.

You should also read the following documents:

https://wiki.openstack.org/wiki/Documentation/HowTo/FirstTimers

https://wiki.openstack.org/wiki/How_To_Contribute

https://wiki.openstack.org/wiki/Documentation/HowTo

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From anne at openstack.org  Fri Sep 26 13:40:15 2014
From: anne at openstack.org (Anne Gentle)
Date: Fri, 26 Sep 2014 08:40:15 -0500
Subject: [Openstack-docs] Getting started
In-Reply-To: <001d01cfd95f$2804fdd0$780ef970$@gmail.com>
References: <001d01cfd95f$2804fdd0$780ef970$@gmail.com>
Message-ID: <CAD0KtVGjDYsyw3a0FumgCgHpnE6iMBUbH7fZCL=o9a9AL==z_g@mail.gmail.com>

On Fri, Sep 26, 2014 at 2:54 AM, Bas Peters <baspeters93 at gmail.com> wrote:

> Hey everyone,
>
>
>
> I?m new to the mailing list (and Openstack in general) and would like to
> start contributing now that I have some more time on my hands. Problem is I
> just rolled out of college and have never seriously contributed to an open
> source project. What?s the best way for me to get started? I saw an e-mail
> come by about install-guide testing and logging bugs against any errors I
> might find. I was wondering if there?s some coordinating mechanism in place
> so I can see what distribution I could best focus on?
>
>
>

Great thinking -- and those links will help. As a summary of the groupings
by distro:

Ubuntu: we know the issues and Matt Kassawara (Sam-I-Am on IRC) is in
contact with their packagers
RHEL/CentOS/Fedora: Matt has started testing and about 2 weeks ago Steve
Gordon said they're running CI on M-3 based packages for RDO.
OpenSUSE: Not sure of their status for packaging.
Debian: quite outdated even for the previous release

Also refer to Matt's status page at
https://wiki.openstack.org/wiki/Documentation/InstallationGuideJuno
 with nice groupings per project. As always Networking/neutron needs lots
of testing.

Appreciate you asking -- feel free to ask more questions on the list or on
IRC (freenode) #openstack-doc.

Thanks,
Anne


> With kind regards,
>
>
>
> Bas
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140926/90c18228/attachment.html>

From mkassawara at gmail.com  Fri Sep 26 15:11:24 2014
From: mkassawara at gmail.com (Matt Kassawara)
Date: Fri, 26 Sep 2014 10:11:24 -0500
Subject: [Openstack-docs] Juno Install Testing
In-Reply-To: <54250A84.1020508@openstack.org>
References: <54250A84.1020508@openstack.org>
Message-ID: <CABA+jQpkqY7=TZ0Gmqe0Cxrd=5_Wf_WO0pVhK5eoQ-j6yvFzCg@mail.gmail.com>

I hear neutron works these days. :)

On Fri, Sep 26, 2014 at 1:41 AM, Tom Fifield <tom at openstack.org> wrote:

> Hi all,
>
> Finally found some time to do a bit of testing on Juno.
>
> Using our Ubuntu 14.04 install guide with just one modification (using
> the staging PPA, rather than the not-yet-ready cloud archive), with
> milestone 3 packages, here's the good news:
>
> * Keystone works
> * Glance works
> * Nova install with nova-network works
>
> and the bad bits:
> * ubuntu-cloud-archive:juno is not ready
> * horizon does not work due to a dependency problem
> (
> https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1374273
> )
>
> So far haven't tested other projects, but at least for these the docs
> look in good shape.
>
> Tracking testing progress @
> https://wiki.openstack.org/wiki/JunoDocTesting#Install_Guide - please
> join in if you have time :)
>
>
> Regards,
>
>
> Tom
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140926/3ac9eedf/attachment.html>

From berendt at b1-systems.de  Fri Sep 26 16:34:42 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Fri, 26 Sep 2014 18:34:42 +0200
Subject: [Openstack-docs] Getting started
In-Reply-To: <CAD0KtVGjDYsyw3a0FumgCgHpnE6iMBUbH7fZCL=o9a9AL==z_g@mail.gmail.com>
References: <001d01cfd95f$2804fdd0$780ef970$@gmail.com>
 <CAD0KtVGjDYsyw3a0FumgCgHpnE6iMBUbH7fZCL=o9a9AL==z_g@mail.gmail.com>
Message-ID: <542595A2.9080700@b1-systems.de>

On 09/26/2014 03:40 PM, Anne Gentle wrote:
> OpenSUSE: Not sure of their status for packaging.

It looks like the Juno packages are not ready at the moment.

Christian.

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From phil.hopkins at rackspace.com  Fri Sep 26 20:01:05 2014
From: phil.hopkins at rackspace.com (Phil Hopkins)
Date: Fri, 26 Sep 2014 20:01:05 +0000
Subject: [Openstack-docs] Juno Install Testing
In-Reply-To: <CABA+jQpkqY7=TZ0Gmqe0Cxrd=5_Wf_WO0pVhK5eoQ-j6yvFzCg@mail.gmail.com>
References: <54250A84.1020508@openstack.org>,
 <CABA+jQpkqY7=TZ0Gmqe0Cxrd=5_Wf_WO0pVhK5eoQ-j6yvFzCg@mail.gmail.com>
Message-ID: <FBC99830465C784CAF93C211A517C0F493E3F18A@ORD1EXD01.RACKSPACE.CORP>

I have Neutron HArouters on Linuxbridge and DVR routers on OVS working from a source install.

[X][X][X][X]
Phil Hopkins RHCA CMDBA
Openstack Instructor
Rackspace Hostingtm
(210) 312-3584
________________________________
From: Matt Kassawara [mkassawara at gmail.com]
Sent: Friday, September 26, 2014 10:11 AM
To: Tom Fifield
Cc: openstack-docs at lists.openstack.org
Subject: Re: [Openstack-docs] Juno Install Testing

I hear neutron works these days. :)

On Fri, Sep 26, 2014 at 1:41 AM, Tom Fifield <tom at openstack.org<mailto:tom at openstack.org>> wrote:
Hi all,

Finally found some time to do a bit of testing on Juno.

Using our Ubuntu 14.04 install guide with just one modification (using
the staging PPA, rather than the not-yet-ready cloud archive), with
milestone 3 packages, here's the good news:

* Keystone works
* Glance works
* Nova install with nova-network works

and the bad bits:
* ubuntu-cloud-archive:juno is not ready
* horizon does not work due to a dependency problem
(https://bugs.launchpad.net/ubuntu/+source/openstack-dashboard/+bug/1374273)

So far haven't tested other projects, but at least for these the docs
look in good shape.

Tracking testing progress @
https://wiki.openstack.org/wiki/JunoDocTesting#Install_Guide - please
join in if you have time :)


Regards,


Tom

_______________________________________________
Openstack-docs mailing list
Openstack-docs at lists.openstack.org<mailto:Openstack-docs at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140926/dc21c0d4/attachment.html>

From sgordon at redhat.com  Fri Sep 26 23:44:48 2014
From: sgordon at redhat.com (Steve Gordon)
Date: Fri, 26 Sep 2014 19:44:48 -0400 (EDT)
Subject: [Openstack-docs] Getting started
In-Reply-To: <CAD0KtVGjDYsyw3a0FumgCgHpnE6iMBUbH7fZCL=o9a9AL==z_g@mail.gmail.com>
References: <001d01cfd95f$2804fdd0$780ef970$@gmail.com>
 <CAD0KtVGjDYsyw3a0FumgCgHpnE6iMBUbH7fZCL=o9a9AL==z_g@mail.gmail.com>
Message-ID: <85373629.27922120.1411775088148.JavaMail.zimbra@redhat.com>

----- Original Message -----
> From: "Anne Gentle" <anne at openstack.org>
> To: "Bas Peters" <baspeters93 at gmail.com>
> 
> On Fri, Sep 26, 2014 at 2:54 AM, Bas Peters <baspeters93 at gmail.com> wrote:
> 
> > Hey everyone,
> >
> >
> >
> > I?m new to the mailing list (and Openstack in general) and would like to
> > start contributing now that I have some more time on my hands. Problem is I
> > just rolled out of college and have never seriously contributed to an open
> > source project. What?s the best way for me to get started? I saw an e-mail
> > come by about install-guide testing and logging bugs against any errors I
> > might find. I was wondering if there?s some coordinating mechanism in place
> > so I can see what distribution I could best focus on?
> >
> >
> >
> 
> Great thinking -- and those links will help. As a summary of the groupings
> by distro:
> 
> Ubuntu: we know the issues and Matt Kassawara (Sam-I-Am on IRC) is in
> contact with their packagers
> RHEL/CentOS/Fedora: Matt has started testing and about 2 weeks ago Steve
> Gordon said they're running CI on M-3 based packages for RDO.

We're gearing up for a test day on Oct 1/2:

https://repos.fedorapeople.org/repos/openstack/openstack-juno/

> OpenSUSE: Not sure of their status for packaging.
> Debian: quite outdated even for the previous release
> 
> Also refer to Matt's status page at
> https://wiki.openstack.org/wiki/Documentation/InstallationGuideJuno
>  with nice groupings per project. As always Networking/neutron needs lots
> of testing.
> 
> Appreciate you asking -- feel free to ask more questions on the list or on
> IRC (freenode) #openstack-doc.
> 
> Thanks,
> Anne
> 
> 
> > With kind regards,
> >
> >
> >
> > Bas
> >
> > _______________________________________________
> > Openstack-docs mailing list
> > Openstack-docs at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> >
> >
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 

-- 
Steve Gordon, RHCE
Sr. Technical Product Manager,
Red Hat Enterprise Linux OpenStack Platform


From berendt at b1-systems.de  Mon Sep 29 12:35:48 2014
From: berendt at b1-systems.de (Christian Berendt)
Date: Mon, 29 Sep 2014 14:35:48 +0200
Subject: [Openstack-docs] Networking Guide not linked on docs.openstack.org
Message-ID: <54295224.9000406@b1-systems.de>

Why is the networking guide not yet linked on docs.openstack.org? Should
this be changed?

-- 
Christian Berendt
Cloud Solution Architect
Mail: berendt at b1-systems.de

B1 Systems GmbH
Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


From aj at suse.com  Mon Sep 29 12:44:26 2014
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 29 Sep 2014 14:44:26 +0200
Subject: [Openstack-docs] Networking Guide not linked on
	docs.openstack.org
In-Reply-To: <54295224.9000406@b1-systems.de>
References: <54295224.9000406@b1-systems.de>
Message-ID: <5429542A.9000407@suse.com>

On 09/29/2014 02:35 PM, Christian Berendt wrote:
> Why is the networking guide not yet linked on docs.openstack.org? Should
> this be changed?

We only link documents of a certain quality and completeness.

Right now the Networking Guide isn't finished, so we're not linking to it.

It should be changed once the guide is good for a "1.0" release ;)

Thanks for checking,
Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From nchase at mirantis.com  Mon Sep 29 12:45:42 2014
From: nchase at mirantis.com (Nick Chase)
Date: Mon, 29 Sep 2014 08:45:42 -0400
Subject: [Openstack-docs] Networking Guide not linked on
	docs.openstack.org
In-Reply-To: <54295224.9000406@b1-systems.de>
References: <54295224.9000406@b1-systems.de>
Message-ID: <CA+p99Gns61BFVkA7tJztp8xgH1znrSM8ht0ROc2X7+FwujX-tA@mail.gmail.com>

No. It's not ready yet. Almost.
On Sep 29, 2014 8:37 AM, "Christian Berendt" <berendt at b1-systems.de> wrote:

> Why is the networking guide not yet linked on docs.openstack.org? Should
> this be changed?
>
> --
> Christian Berendt
> Cloud Solution Architect
> Mail: berendt at b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstra?e 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140929/4bdb87c2/attachment.html>

From nchase at mirantis.com  Mon Sep 29 21:06:16 2014
From: nchase at mirantis.com (Nicholas Chase)
Date: Mon, 29 Sep 2014 17:06:16 -0400
Subject: [Openstack-docs] Contributing to docs without Docbook -- YES you
	can!
Message-ID: <5429C9C8.1090400@mirantis.com>

As you know, we're always looking for ways for people to be able to 
contribute to Docs, but we do understand that there's a certain amount 
of pain involved in dealing with Docbook.  So to try and make this 
process easier, we're going to try an experiment.

What we've put together is a system where you can update a wiki with 
links to content in whatever form you've got it -- gist on github, wiki 
page, blog post, whatever -- and we have a dedicated resource that will 
turn it into actual documentation, in Docbook. If you want to be added 
as a co-author on the patch, make sure to provide us the email address 
you used to become a Foundation member.

Because we know that the networking documentation needs particular 
attention, we're starting there.  We have a Networking Guide, from which 
we will ultimately pull information to improve the networking section of 
the admin guide.  The preliminary Table of Contents is here: 
https://wiki.openstack.org/wiki/NetworkingGuide/TOC , and the 
instructions for contributing are as follows:

 1. Pick an existing topic or create a new topic. For new topics, we're
    primarily interested in deployment scenarios.
 2. Develop content (text and/or diagrams) in a format that supports at
    least basic markup (e.g., titles, paragraphs, lists, etc.).
 3. Provide a link to the content (e.g., gist on github.com, wiki page,
    blog post, etc.) under the associated topic.
 4. Send e-mail to reviewers networking at openstacknow.com.
 5. A writer turns the content into an actual patch, with tracking bug,
    and docs reviewers (and the original author, we would hope) make
    sure it gets reviewed and merged.


Please let us know if you have any questions/comments.  Thanks!

----  Nick
-- 
Nick Chase
1-650-567-5640
Technical Marketing Manager, Mirantis
Editor, OpenStack:Now
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140929/1a58bea5/attachment.html>

From akilesh1597 at gmail.com  Tue Sep 30 04:03:20 2014
From: akilesh1597 at gmail.com (Akilesh K)
Date: Tue, 30 Sep 2014 09:33:20 +0530
Subject: [Openstack-docs] [openstack-dev] Contributing to docs without
	Docbook -- YES you can!
In-Reply-To: <5429C9C8.1090400@mirantis.com>
References: <5429C9C8.1090400@mirantis.com>
Message-ID: <CAFafR-n5TkfV9_7vwBoEKpiKKwxRcpV19H4TQptKokaAP+LzXw@mail.gmail.com>

Hi,
I saw the table of contents. I have posted documents on configuring
openstack neutron-openvswitch-plugin, comparison between networking devices
and thier linux software components and also about the working principles
of neutron-ovs-plugin at layer 2 and neutron-l3-agent at layer 3 . My
intention with the posts was to aid begginers in debugging neutron issues.

The problem is that I am not sure where exactly these posts fit in the
topic of contents. Anyone with suggestions please reply to me. Below are
the link to the blog posts

1. Comparison between networking devices and linux software components
<https://fosskb.wordpress.com/wp-admin/post.php?post=2781&action=edit>
2. Openstack ovs plugin configuration for single/multi machine setup
<https://fosskb.wordpress.com/wp-admin/post.php?post=2605&action=edit>
3. Neutron ovs plugin layer 2 connectivity
<https://fosskb.wordpress.com/wp-admin/post.php?post=2755&action=edit>
4. Layer 3 connectivity using neutron-l3-agent
<https://fosskb.wordpress.com/wp-admin/post.php?post=2910&action=edit>

I would be glad to include sub sections in any of these posts if that helps.

Thank you,
Ageeleshwar K

On Tue, Sep 30, 2014 at 2:36 AM, Nicholas Chase <nchase at mirantis.com> wrote:

>  As you know, we're always looking for ways for people to be able to
> contribute to Docs, but we do understand that there's a certain amount of
> pain involved in dealing with Docbook.  So to try and make this process
> easier, we're going to try an experiment.
>
> What we've put together is a system where you can update a wiki with links
> to content in whatever form you've got it -- gist on github, wiki page,
> blog post, whatever -- and we have a dedicated resource that will turn it
> into actual documentation, in Docbook. If you want to be added as a
> co-author on the patch, make sure to provide us the email address you used
> to become a Foundation member.
>
> Because we know that the networking documentation needs particular
> attention, we're starting there.  We have a Networking Guide, from which we
> will ultimately pull information to improve the networking section of the
> admin guide.  The preliminary Table of Contents is here:
> https://wiki.openstack.org/wiki/NetworkingGuide/TOC , and the
> instructions for contributing are as follows:
>
>
>    1. Pick an existing topic or create a new topic. For new topics, we're
>    primarily interested in deployment scenarios.
>    2. Develop content (text and/or diagrams) in a format that supports at
>    least basic markup (e.g., titles, paragraphs, lists, etc.).
>    3. Provide a link to the content (e.g., gist on github.com, wiki page,
>    blog post, etc.) under the associated topic.
>    4. Send e-mail to reviewers networking at openstacknow.com.
>    5. A writer turns the content into an actual patch, with tracking bug,
>    and docs reviewers (and the original author, we would hope) make sure it
>    gets reviewed and merged.
>
>
> Please let us know if you have any questions/comments.  Thanks!
>
> ----  Nick
> --
> Nick Chase
> 1-650-567-5640
> Technical Marketing Manager, Mirantis
> Editor, OpenStack:Now
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140930/6982e5a6/attachment-0001.html>