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

Lana Brindley openstack at lanabrindley.com
Thu May 28 03:24:36 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That's great news, thank you!

L

On 28/05/15 13:23, Shilla Saebi wrote:
> 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:
> 
> 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
>>>>
>
>>>> 
> 
>> 
>> _______________________________________________ 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

iQEcBAEBAgAGBQJVZop0AAoJELppzVb4+KUyXDoH/AuslKZh3yWg09jaUdgm9G9A
YqC8/4H8I/UDw99MCNOdP+W834opb1Lp631ONN7bBqMsBVnbcocdgCYuKlfIe9lG
3QYUScNpFHxencJapeKCFl9gfNIZvhEkmir9o3vSL9cej5F4Hq1s5AYKkF3ZLExh
/UZiH0g59Doi8BcfZl4evPDpwefvWONL8MAJdxpK49SyQdpBcQkxcAKgm0eJOoGd
tkeV4YHcvY4oejdGqtgMtF4WsbTmtkD+7TZaDoxbqX+hgWTcDx8ifASg0I0oM/qZ
NQopKMY/0a1BByjIEwP5/cVj20VFp9eX9DEN2p6WEetz3Qk+2fEBod8WkWpiH4g=
=JzrV
-----END PGP SIGNATURE-----



More information about the OpenStack-docs mailing list