[OpenStack-docs] Install Guide - troubleshooting section?

Lana Brindley openstack at lanabrindley.com
Mon Apr 10 21:31:09 UTC 2017

On 10/04/17 18:43, Alexandra Settle wrote:
> On 4/10/17, 12:24 AM, "Lana Brindley" <openstack at lanabrindley.com> wrote:
>     On 08/04/17 02:35, Amy Marrich wrote:
>     > So this week there was a post about rabbitmq connecting locally on nova after an upgrade to Ocata. A day or so later I had someone running through my Install OpenStack Newton course run into the same issue but on neutron. The fix was to add the transport_url under [oslo_messaging_notifications] and not just in [DEFAULT] in both cases. This doesn't even touch on the never bugged need for a newer version of pyelibc and liberasurecode1 for swift on ubuntu which has now been updated as I mentioned it in passing to Corey while working on something else.
>     > 
>     > Many people are not on openstack-dev and we have folks asking and solving questions there as well as on ask.o.o, and the openstack and openstack-operators lists. And just cause we work around it doesn't mean new folks can do the same.
>     > 
>     > So my question to everyone is do we need a section in the docs for 'You May Need to Do This' type settings like the first example, as well as chown on directories for cinder, etc. if we see it come up more then once or if we 'work around it' during our own testing/installations.
>     I like the idea of a 'things that might trip you up' type section, although maintenance of it would be the real problem.
> I agree, maintenance could be a big problem (which is not something I thought about when Amy mentioned this to me) and we really are trying to deal with the amount of technical debt we already have.
> On the other hand, we do want to lower the barrier to entry and make it easier for first time users. Maybe we could have something on the wiki? Something that is linked out, and maintained by the users?

Wiki is awkward, because of the limitation on accounts, etc (thanks to the spam problem). Also, I don't really see the wiki as a better solution than ask.o.o. The more I think about this, I think what needs to happen is that people answering questions on ask.o.o should be more vigilant about creating docs bugs. That way we can triage the content properly, and add it in to the appropriate place in the first instance (rather than piling things into a catch-all section, which will then need to be tidied on a regular basis).


Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 538 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20170411/76b59730/attachment.sig>

More information about the OpenStack-docs mailing list