Open Stack

My opinion is that the HA Guide can reasonable expect an audience that isa little bit sophisticated and so can handle some distro-specific details sprinkledaround.  In fact, I rather like that -- it makes it easier to figure out what the distro-specific issues are.
As I understand it, the Install Guides are split by distro because they are writtento be appropriate for people who are neophytes and they embed a lot of distro-specific admin information that is tangential to OpenStack but people may need.
Bogdan, you've spent a lot of time on the phone with the people who are the targetaudience for this book and I know from experience that you have awfully good judgementabout the information that need to be included.  So, if there is a tidbit that you think isappropriate, I'm pretty confident that it should be included.  Your knowledge and judgementis one of the great advantages of having you take over this project!
meg
 
      From: Lana Brindley <openstack at lanabrindley.com>
 To: openstack-docs at lists.openstack.org 
 Sent: Saturday, October 17, 2015 6:38 PM
 Subject: Re: [OpenStack-docs] [ha-guide] Distro specific details to improve UX
   
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I don't see a big problem with mentioning some OS-specific stuff in cases like 235893. It's useful troubleshooting info in this case. 

L

On 17/10/15 00:36, Matt Kassawara wrote:
> Adding the review here...
> 
> https://review.openstack.org/#/c/235893/
> 
> On Fri, Oct 16, 2015 at 8:32 AM, Bogdan Dobrelya <bdobrelia at mirantis.com>
> wrote:
> 
>>
>> Hello.
>> There are UX bugs, like [0], [1]. These might make a user following the
>> guide steps very sad because the corosync/pacemaker services will refuse
>> to start. How should we deal with such issues?
>>
>> May be sometimes, the distro specific info should be accepted into the
>> HA guide?
>>
>> Or should we just mention there are distro specific configuraion steps
>> exist and leave a user on his own in his/her search of external docs
>> explainging the distro specific steps TBD?
>>
>> Note, the same question applies to the distro specific pcs/crm cluster
>> configuration tools.
>>
>> [0] https://bugs.launchpad.net/openstack-manuals/+bug/1505964
>> [1] https://bugs.launchpad.net/openstack-manuals/+bug/1506004
>>
>> --
>> Best regards,
>> Bogdan Dobrelya,
>> Irc #bogdando
>>
>> _______________________________________________
>> 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 v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJWIvgWAAoJELppzVb4+KUy/ZwIAMZz8iPv25hjAsj9g/JOgyWt
oJXZLTVYfyxSClC0lXqId9IIDYd74/1I1NwyJi6UmKPIAKOIhtgnGKRe+Jucp5yo
8c0CetOlRJB+lzJ99R0bE84U39Jujbz5MtoLowGWmBJBn6ExKICHzm2PdisxGdog
OLZXTPsI6nrPPhzxSKkbrzrnop1if34HZqdcSZszmkqtmFMMhPjs6EAD9L6Y4ZG0
hhN0U+uEFmPKq4KBxYzXsEh+DrgVbrxPf7p/DkJEIFXHqa86aooRncFTKgiDApwd
sLcGVeF6I2uqy4KlvZaVvIdc/AEloMzLUjoXWy6HyphvOzVPb26erdAYn5/XLbo=
=Jiln
-----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/20151018/8e9f3a79/attachment.html>