4 Clicks takes you to http://devstack.org/ and installs with 2 commands... git clone https://github.com/openstack-dev/devstack.git then cd devstack && ./stack.sh
That's not the same as getting the whole thing running of course, but getting to a simple-looking set of instructions is pretty quick.
I was following this project instead:
It is a project that basically lets you manage a set of libvirt based host machines. Nothing cloud scale or anything like that just something for a small business.
Here is the architecture. It is too bad this doesn't get more press as it seems simpler and easier to understand.
I recently evaluated ovirt in a small business context, and one of the stumbling blocks was, "how do I specify which VMs should be automatically run at boot time, and how do I control the order in which they boot?" The current answer to that with ovirt is in effect: "Well, we expect you to have a highly-availble bunch of management nodes which will simply remember what the set of currently running VMs ought to be. If that doesn't float your boat, maybe you should use the API and roll your own control system."
From a small business context this basically amounts to: No.
Note that this is not a serious criticism of ovirt. A project has finite resource, there's only so many things they can focus on at one time, I fully expect that things will improve over time, and the stuff that is there installs and runs very smoothly.
Found that in about 30 secs from the OpenStack site.
It took a few hours of following the instructions to the letter but everything worked first time and it's fairly par for the course in terms of installing a complex bit of software.
I am going through a complex install at the moment, and I am sitting in IRC with openstack developers to help solve issues.
I've done that with many packages in my life, so I don't think that's odd, but to be fair.. I have no idea how I'd be progressing without asking individuals in IRC on specific points.
Starting from the home page (http://openstack.org), try to download something that will let you run a test stack on your local machine, and run it. Time how long this takes.
For me, it took over 50 clicks, searches, etc. and two hours of time before I figured out how to get the stack up and running. It was one of the most frustrating technology experiences I've had in recent memory. The website is a labyrinthine, confusing morass of marketing gobbledygook that I found difficult to get important details from, at least for developers as an audience.
I think OpenStack has a long way to go in terms of technical usability before I'd consider trying it out again. That was months ago (August 2013), so maybe things have improved, but I haven't worked up the courage to try again just yet.
P.S. OpenStack devs: I'd be happy to have a conversation about it! I would love to be told that my experience was anomalous and get a reason to give it another shot.