Open Stack

I do have a request. Can we make sure the identification of this problem 
is easily searchable if one uses a command or keyword that an operator 
would use that may trigger this outcome?

My reasons for my request:
I got caught in a similar issue when following the instructions for a 
project which OpenStack Infra uses but which is not OpenStack. The 
operating code was installed using defaults. I followed the 
documentation (I am an intern) and wrote a patch which implemented a 
command the project recommended as part of the maintenance for that 
project. The command was executed and the combination of the suggested 
command and our default installation created a bloated db file causing 
problems for the expected operation of the application.

Prior to implementing the suggested command, I did google it and came up 
only with the project's documentation recommending the use of it. It was 
a very specific command and I didn't come up with any results other than 
the project documentation. I did not know that given our default db 
set-up with the project that this command could create an unwanted 
situation. Had I had access to any documentation identifying specific 
circumstances in which the command might cause problems, I would have 
followed the steps to identify our set-up and changed our db 
configuration so the command could be executed safely. (I am currently 
working on a patch to do exactly that, which I intend to blog about 
using the command as a title for my blog post.)

I feel embarrassed at the situation, I created a bomb which my colleague 
has to clean up, and disappointed that while experienced users of the 
project knew that our particular configuration would cause problems, 
there was no further or suggested reading attached to the documentation 
or as a result from a search of the command. As an intern I recognize 
that when I fall in a hole it is mine to climb out of, but offering our 
users rope ladders in these situations helps us to have more users, at 
least from my point of view.

Thanks for considering my request,
Anita.


On 13-03-17 08:52 AM, Michael Still wrote:
> On Sat, Mar 16, 2013 at 10:45 PM, Davanum Srinivas <davanum at gmail.com> wrote:
>> Lorin,
>>
>> Dumb question - are the existing mechanisms to raise feature requests
>> lacking? (Can devs assume that ops folks will open a new bug in
>> launchpad?)
> Yeah, that was kind of my point. I only know what I am told. The
> correct process to report problems or experiences you didn't enjoy is
> to file detailed bugs on launchpad.
>
> Michael
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>