Open Stack

----- Original Message -----
> From: "Anne Gentle" <annegentle at justwriteclick.com>
> To: "Shaun McCance" <shaunm at gnome.org>
> Cc: openstack-docs at lists.openstack.org
> Sent: Thursday, July 18, 2013 12:30:45 PM
> Subject: Re: [Openstack-docs] Intro and example installations
> 
> 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

I have two questions here, the answers to which would help me better form my thoughts on this:

1) Wasn't nova-volumes removed in Grizzly ( https://blueprints.launchpad.net/nova/+spec/delete-nova-volume )?
2) Isn't nova-network slated to be deprecated in Havana ( https://blueprints.launchpad.net/nova/+spec/deprecate-nova-network )?

I know the intent is to "keep it simple stupid" but is it realistic to continue to avoid Cinder and Neutron at this point if their predecessors are on the way out the door? Admittedly networking in neutron is more complicated for the simple case than it is in nova-network, and deprecation doesn't (yet) mean removal, but thought I would pose the question. It is of course possible I have misinterpreted the outcomes of the above blueprints :).

I think you could get away with not doing block storage using nova-volumes or Cinder at all in the most basic architecture and then provide it as the first "bolt on" component.

Thanks,

Steve


> 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?