Open Stack

Matt,

My thoughts:
1. I believe bus will be easier to track but it means for a lot of bugs to be created.

2. For now lets keep the DVR stuff in the Networking/admin guide. It avoids massive changes to the install guides - for now.

3. I really like using Linux Bridge over OVS, but again I think minimizing changes to the install guide will help use get something usable by Juno release. Lets look at adding that material later.

4. make it flat.

5. Again my preference is to get Juno install done first. Add new material later. SPICE would be a ggod change but lets roll that out later. novnc woks fine for now.

 6. We need to go to MariaDB (RHEL7 only has MariaDB). Again lets plan on moving but it doesn't need to be done on first release.

I know this seems like I am in favor of putting everything off, but I want us to have a workable manual out on Juno release time. I don't see any of these items as necessary on release date.

[X][X][X][X]
Phil Hopkins RHCA CMDBA
Openstack Instructor
Rackspace Hostingtm
(210) 312-3584
________________________________
From: Matt Kassawara [mkassawara at gmail.com]
Sent: Wednesday, September 10, 2014 1:17 PM
To: openstack-docs at lists.openstack.org
Subject: [Openstack-docs] Installation guide updates for Juno

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.

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.

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?

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.

5) I'm seeing more deployments moving from novnc to spice consoles. Should we configure spice instead of novnc?

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?

[1] https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/juno-staging

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140910/b78d842a/attachment-0001.html>