Open Stack

Hi Ed,

Well its certainly more basic in that it has fewer nodes...
>

Only one less node. I felt that the Quantum controller parts make sense on
the cloud controller -- especially for a basic install guide.

If one does have a good reason to do this, it will not be hard to describe
in a separate document using the first as a reference.


> well from the quantum side the answer would certainly be no.
>
> No sep management network.
>

I didn't feel there was a need for this in a basic install guide. This
guide shows a "data network" which lays the groundwork for multiple other
networks. For example, the data network can be a 10gb connection. The basic
guide assumes one type of traffic, though it's not a far stretch to turn
that into separated traffic using VLANs but still be on the physical
network.


> No connection (even temporary for the compute nodes to reach the outside
> world to load packages)
> muddling network and control functionality.
>

Instances have NAT'd guest access at the end of this guide. The only thing
missing is Floating IPs but that's because I felt I ran out of time. I can
work on this in the next week.

Regarding compute node connectivity, this is true and it's something I
overlooked. I can easily modify this document to show how the cloud
controller can NAT traffic for the compute node. Or the compute node could
be given its own gateway - however, I'm not sure what the status of
multi-host quantum networking is, so that's why I tunneled all instance
traffic to the cloud controller.


> In the old form there was at least some room to say "Follow this guide
> except for the quantum bits"
> Now that while you've accomplished your goal of lean and mean I'm going to
> need folks to go back
> altering host files, altering the db and endpoints…as well as all the
> changes to re-create the mgmt network.
>

This guide is all about foundation. It shows the reader how to install the
various OpenStack components using the ubuntu cloud archive, what
configuration files for each component need edited, how to make them all
work together, and successfully launch an instance.

After someone goes through this guide, I think it's safe to say that they
will understand what you're trying to accomplish when you alter this
installation and why you're doing it.

I fully understand that everyone has their own opinion about what an
install guide should look like. This is an unfortunate effect of the lack
of intelligent packages used to install OpenStack. This is my take on it. I
tried to place myself in a new user's shoes when writing and if I felt that
the user simply didn't need to know about a certain area at their novice
stage, I took it out.

Thanks,
Joe


-- 
Joe Topjian
Systems Administrator
Cybera Inc.

www.cybera.ca

Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130420/3fc74dc3/attachment.html>