Open Stack

Great work Shaun! Here are my thoughts for the example architectures.

Simplest possible architecture: Compute with KVM, local ephemeral
nova-volumes shared storage, nova-networks in multi-host, MySQL, nova-api,
default scheduler, RabbitMQ for Ubuntu, Qpid for RHEL, Identity, Image with
local storage, Dashboard. Use as many defaults as you can, as identified by
the deployment program, TripleO. Single node or two node.

Operations Guide example architecture:
http://docs.openstack.org/trunk/openstack-ops/content/example_architecture.html

If you can do these two for your first draft, then here are some additional
alternatives. The most "exciting" is probably Neutron. Block Storage is
most common.

Pivots on Ops Guide example:
1. Substitute Neutron for nova-network, keep everything else the same.
2. Substitute Block Storage for nova-volumes, keep everything else the same.
3. Keep Ops Guide example but backend Image storage with Object Storage.
4. Include Compute, Image, Identity, Block Storage, Object Storage,
Dashboard, Monitoring and Orchestration.

Lower priority:
Sub Xen for KVM.

Anyone else have input for choosing adventures?
Anne

Another note is that legally to call your deployment an OpenStack cloud you
currently must have Compute and Object Storage. No other requirements exist
currently but that will be changing.


On Thu, Jul 18, 2013 at 10:40 AM, Shaun McCance <shaunm at gnome.org> wrote:

> Hi all,
>
> I want to ask the list for input on example installations of OpenStack.
> But since I've failed to introduce myself to the list, let me do that.
>
> I've been doing open source documentation for GNOME for a long time.
> In fact, this September I will have been the GNOME docs team lead for
> ten years. I also run the Open Help Conference each year, which is how
> I met Anne. I do freelance documentation work as a day job. Currently,
> I'm doing upstream OpenStack documentation work under contract with
> Cisco, working on the installation guides.
>
> What I'd like to do is compile a list of example deployments that we
> can use to guide and evaluate the installation docs. Obviously, it
> can't be comprehensive, given how flexible OpenStack is. Thinks of
> personas, except configurations instead of people.
>
> Does anybody have any real-world cases they can distill into examples?
> Ideally we'd have half a dozen example setups: how many nodes, what's
> running on what, etc. More importantly, why was OpenStack set up this
> way, what advantages does it have, and what are the drawbacks.
>
> My general plan is to have a single installation guide, with the first
> couple chapters providing the simplest evolvable installation, and the
> rest being a sort of choose-your-own-adventure on adding to that basic
> installation. Having example setups would help a lot in getting the
> structure right.
>
> Thanks,
> Shaun
>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Anne Gentle
annegentle at justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130718/122e8f70/attachment.html>