[OpenStack-docs] deprecation/future of "OpenStack Operations Guide"

Shilla Saebi shilla.saebi at gmail.com
Thu May 28 03:23:04 UTC 2015


Sure thing, I can take on both guides. Thank you!

Shilla

On Wed, May 27, 2015 at 7:47 PM, Lana Brindley <openstack at lanabrindley.com>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> At Summit, we agreed that the Ops Guide is generally loved, but also
> that it probably needs a refresh. The only other issue around this doc
> was that the upgrades section probably needs to be removed, although we
> hadn't decided on a location for that information.
>
> I agree with Anne that we shouldn't treat the book sprint books as
> second class citizens. For now, there is quite a lot of work planned for
> the Arch Guide, with a two-day docs swarm happening in August to
> concentrate on information architecture.
>
> I also agree with Nick that the two books serve two quite different
> functions, so merging them is not a great idea.
>
> Shilla, if you're willing to head up a docs speciality team to look
> after the Ops Guide, then that's a great idea! Is there a chance you
> could also take on the Arch Guide?
>
> Lana
>
> On 28/05/15 01:26, Shilla Saebi wrote:
> > I volunteer myself as one of the maintainers of the ops guide.
> >
> > On Wed, May 27, 2015 at 10:29 AM, Nick Chase <nchase at mirantis.com>
> wrote:
> >
> >> In fact, the Architecture Guide was specifically written that way to
> avoid
> >> coinciding with the Operations Guide.
> >>
> >> ----  Nick
> >>
> >> On 5/27/2015 9:59 AM, Sean M. Collins wrote:
> >>
> >>> On Wed, May 27, 2015 at 09:54:32AM EDT, Christian Berendt wrote:
> >>>
> >>>> I think today "designing OpenStack clouds" is part of the "OpenStack
> >>>> Architecture Design Guide" and all content related to the design of a
> >>>> OpenStack cloud should be moved there.
> >>>>
> >>> Most of the content in the Architecture Design guide does not go into
> >>> the dirty details of designing your cloud. I have not read the
> >>> Operations Guide, but if it discusses implementation then there will be
> >>> an issue. The Arch Design guide was written about
> >>> architecture, not implementation. Merging this content is not a good
> >>> idea since they have different audiences and topics.
> >>>
> >>>
> >>
> >> _______________________________________________
> >> 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
> >
>
>
> - --
> Lana Brindley
> Technical Writer
> Rackspace Cloud Builders Australia
> http://lanabrindley.com
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJVZlehAAoJELppzVb4+KUyliwIAJVN8QLWNW6przQjWqKqtzBu
> hXgiJNxUHkVQR5txLraXeKaKP1xYjDUCVIkgJuv9iCAUSJkMzDiXeObkeOz4L+Zp
> 0Rw9syM/jwFfig7M90vWDdhjX27+rdLTSY47RPxOwwq+Al47trSNa+Aie+HQI2Xm
> 74PVaJkxg59P9UadM3r7lgADhvDLVeNXE7leblISdtVNv3JDdzIybwI0sSpPKQyi
> DYPsswrkpVm2W6BTt7hQt37D3NySaut+ZBpGE+MbLlRH+EED0xnMfABStZfI1gA2
> x163bmokLKUdqDOMpIyg3/3b/AUz+XUowuogzau8Ysnq8SvwVeCzcFaVeHzMrLM=
> =OXnP
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> 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/20150527/0dfa16bf/attachment-0001.html>


More information about the OpenStack-docs mailing list