Open Stack

Excerpts from Turbo Fredriksson's message of 2016-10-11 10:21:32 +0100:
> On Oct 10, 2016, at 6:33 PM, Clint Byrum wrote:
> 
> > I don't think anyone should use devstack for anything except developing
> > openstack. It's not for anything else.
> 
> THANK YOU! :)
> 
> > We're just trying to point out that you're taking the hardest possible
> > approach, and many of us who had to go down that road before, would like
> > to stop spending time assisting anyone who is unnecessarily repeating
> > our work.
> 
> Well, I've been working and participating in a lot of Opensource projects
> over the last twenty years, and every single one have had things they could
> learn from their users.
> 
> _I_ learned to hate the "stupid questions" that always kept cropping up,
> so I either wrote code to stop it from happening again, or I wrote documentation.
> 

We wrote at least 7 fully open source deployment systems so you can just
deploy OpenStack, and we have installation manuals. Not sure what more
we are supposed to do here. If you're dead set on writing more
deployment systems, I suggest you reevaluate your priorities.

> "The Openstack Community" (as a whole, looking at _all_ the projects under
> that flag) isn't the worst, but it's down there somewhere at the bottom..
> 
> I might not be the most PC guy, but I know for a fact that I'm not alone in
> this view. I've talked to a lot of people over the years that either
> _wanted_ to try OS, _was_ trying it or was _thinking_ about it.
> 
> But everyone have basically had the same experience that I have had since
> I forced myself to actually commit to this in April/May - OS is badly
> documented, the community is rude and unhelpful and it's a pain in the
> behind [to get things working].
> 

"People are saying, I've heard, I'm just saying". Sounds like the Trump
method of fact gathering.

The community is really busy solving new issues. We solved this a long
time ago. I'm sorry that you're not getting what you want out of
OpenStack, but we can't be everything to everyone and still accomplish
anything of value.

> 
> Now, you're all free to take what you want from that. Take it as a grave
> insult to your manhood and/or coding/documentation skills what have you..
> 
> 
> Or you can be a grownup, acknowledge your imperfections and strive to do
> better.
> 
> > Doing it your way means losing all of that momentum
> 
> Then YOU have missed MY point :(
> 
> 
> Whenever ANYONE is asking ANY type of question, it means the documentation
> (or code) isn't clear.. Leave it as-is (and keep having to "go backwards"
> every time someone asks a/that question), or improve on it. It's a binary
> choice..

What part of this manual is deficient for people who want to install
Trove?

http://docs.openstack.org/developer/trove/dev/manual_install.html#source-images

And if you want to know how those are built:

http://docs.openstack.org/developer/trove/dev/building_guest_images.html

So, to reiterate what more do you want?