Open Stack

On Wed, Sep 10, 2014 at 1:17 PM, Matt Kassawara <mkassawara at gmail.com>
wrote:

> Ubuntu recently began offering pre-release Juno packages [1] and I
> successfully built a three-node "core services" environment using them.
> Let's discuss the potential changes...
>
> 1) So far, updating the OpenStack services chapters of the installation
> guide mostly involves some configuration file changes, removing old
> workarounds, and probably adding new workarounds. Should we use a bug or a
> blueprint for these issues? In either case, I recommend uploading separate
> patches for each service.
>
> First off, so glad you're paying attention and have the eye for this work.

Definitely separate patches will be easier to review. I think you should
track with the Juno install guide blueprint at
https://blueprints.launchpad.net/openstack-manuals/+spec/installation-guide-improvements
-- sound good?


> 2) Neutron supports distributed virtual routers (DVR) and I'm sure people
> want instructions for deploying them. However, DVR introduces more
> complexity to already difficult networking concepts and requires
> architectural changes to fully configure and demonstrate. At least for
> Juno, I recommend keeping the legacy architecture and adding instructions
> for deploying DVR to the networking or admin guides.
>
>
Yeah, let's keep DVR in a separate guide. Install Guide is meant for happy
path, get-an-instance-bootable architecture.


> 3) Open vSwitch adds another level of complexity to already difficult
> networking concepts, particularly with troubleshooting. Linux Bridge
> provides a reliable alternative that reduces complexity, but DVR doesn't
> support it. Should we add instructions for deploying Linux Bridge as an
> alternative to Open vSwitch?
>
>
I wouldn't add it to the install guide.

What I do hear from others is that OVS is not easily understood because
it's less deployed, but that's just rumor really. Still, now's the perfect
time to ask the question and visit the answer.


> 4) The neutron external network (ext-net) "magically" works although we
> don't explicitly configure support for flat networks. For sanity, we should
> probably adjust the configuration to support one flat network and adjust
> the initial network instructions to use it as a flat provider network.
>
>
Man it would be great to support one flat network. Is that then making for
three networking architectures? I'm not opposed, just making sure I
understand.


> 5) I'm seeing more deployments moving from novnc to spice consoles. Should
> we configure spice instead of novnc?
>
>
Nah, less change is better for that. More NoVNC in the field also I believe.


> 6) I'm seeing more deployments moving from MySQL to MariaDB. Ubuntu 14.04
> offers MariaDB 5.5 which more or less clones MySQL 5.5 including the
> configuration files. I suspect RHEL 7, Fedora, and other RPM distributions
> also offer MariaDB packages. Should we change all distributions to MariaDB?
>

It will make maintenance easier, and sounds like it's possible with Kilo,
but not yet with Juno. So... sorry.

To summarize:
Use
https://blueprints.launchpad.net/openstack-manuals/+spec/installation-guide-improvements
for tracking.

As little change as possible. Update to MariaDB as you can. Add flat
network if possible.

Thanks Matt for doing this!
Anne


>
> [1]
> https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/juno-staging
>
> Matt
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140911/432c939e/attachment.html>