Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of runseb@gmail.com designates
 74.125.83.41 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [DOCS] Using Includes in the Administration Guides
From: sebgoa <runseb@gmail.com>
In-Reply-To: 
 <CAC2panqrSKdaKhdKyTO0iAXdRGXPzn_DSp-Mk+mQqN51p4Xryw@mail.gmail.com>
Date: Tue, 13 May 2014 10:16:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <85D286CF-0EF8-4435-9C25-2970CDE937AD@gmail.com>
References: 
 <CAC2panqrSKdaKhdKyTO0iAXdRGXPzn_DSp-Mk+mQqN51p4Xryw@mail.gmail.com>
To: dev@cloudstack.apache.org


On May 12, 2014, at 4:29 PM, Will Stevens <wstevens@cloudops.com> wrote:

> Hi All,
> I have been building documentation for the Palo Alto Networks firewall
> integration which I would like to add to the Administration Guide.
>=20
> I have currently built the Palo Alto integration doc as a stand alone =
doc,
> but I will be tweaking it in order to include it in
> the Administration Guide.
>=20
> Looking at the Administration Guide, I am noticing that the 'Managing
> Networks and Traffic' section is very long and a bit difficult to =
manage as
> it is.
>=20
> I am wondering if it makes sense to have a 'networking' folder and =
each of
> the subsections in that section be broken out into its own file which =
is
> then included into the 'networking2.rst' file.
>=20
> I am willing to work on this if you agree that this will simplify the
> management of this section of the documentation.
>=20

+1

The all networking section in the admin guide needs to be cleaned up, =
there are currently three files:
-networking.rst
-networking2.rst
-managing_networks.rst

these files may have duplication and need to be organized much better

have at it

-sebastien

> Cheers,
>=20
> Will