Open Stack

On 02/06/2015 07:16 PM, Anne Gentle wrote:
> Hi again all, 
> I'm top posting, sorry. I finally had a chance to do more in-depth
> analysis of these bug reports. 
> 
> I hesitated initially on whether to post to the list, since there are a
> lot of hard feelings coming up around this, and people are pretty tired
> of the "drama." But we need to address these issues, and I don't want
> anyone to feel personally tied to the issues. There is no individual
> blame or fault here. That said, as PTL I do need to make a decision
> based on technical merits.
> 
> I did an analysis to see whether the install issues come up from a
> difference in philosophy or bugs in the doc. I'm leaning towards "bugs
> in the doc causing issues" as the final analysis, and I'd like us to
> consider stopping links to the Debian Install Guide until the issues are
> addressed. 
> 
> Here's my analysis.
> 
> Where debconf inconsistency that don't cause failure to install but may
> confuse, these I don't consider as reasons to stop publishing:
> 1. deprecated options in mysql conf
> 2. database names end in db
> 3. uses ip address instead of name
> 4. admin tenant and user instead of separate users and a service tenant
> 5. deprecated xml body middleware and kvs backend for keystone
> 6. debconf doesn't enable verbose logging
> 
> Where there are actual doc bugs due to Debian being different, causing
> problems later:
> 1. rabbitmq bound to 127.0.0.1, perhaps means it thinks of itself as a
> single node install. While this is a philosophical difference, it
> does prevent services on the network and compute nodes from accessing
> the queue.
> 2. glance.conf problem that causes actual warnings [keystone_authtoken]:
> identity_uri must not use localhost
> 3. glance.conf problem that causes actual warnings [keystone_authtoken]:
> auth_uri must be set to public url, clients may not be able to
> authenticate against an admin endpoint
> 4. glance.conf problem: default_store in wrong location, should be in
> [glance_store]
> 5. my_ip incorrectly configured for glance, causing inability to connect
> from a separate server (When launching an instance, Compute attempts to
> contact the image service using the value of the my_ip option). Again
> this is probably due to assuming a single server install.
> 
> nova.conf config:
> (opinion) metadata service enabled, different from other distros
> 6. spice console won't work
> 7. [keystone_authtoken]: identity_uri must not use localhost
> 8. [keystone_authtoken]: auth_uri must be set to public url
> 9.doesn't reference controller node for nova to glance connection (acts
> like single node install)
> 10.problems with needing port 35357 instead of 5000
> (opinion) nova.conf compute node could remove database connection but
> optional
> 
> neutron problems
> (opinion, but may cause problems) doesn't let people choose their own
> network settings
> 11. uses deprecated config files
> 12. local_ip option not there
> 13. metadata agent won't connect to misconfigured database
> 14. 16. same keystone problems as nova and glance
> 15. L2 population won't work
> 
> Overall problems due to basic architecture decisions being different:
> - Debian assumes images served from same node as compute node
> - Debian doesn't have nova-network
> - Debian assumes use of Open vSwitch
> - Debian assumes certain networking settings
> - Debian enables rabbitmq for glance prior to needing it since telemetry
> is optional, so architecture seems to assume telemetry is a requirement.
> 
> I have been mediating this debate since November 2014 so I'd like to get
> forward movement. My analysis indicates the issues are due to too many
> assumptions being made for Debian causing problems. I know Thomas and
> Alex planned to test this week, so I hope they can validate these bugs
> and devise a plan to address them. 
> 
> Based on the plan, we'll make a decision about links and/or redirects.
> 
> Let me know the plans by replying here or responding to the bugs by 2/16/15.

I've seen some of bugs getting triaged but others not getting addressed
at all. So, that means there's currently no plan on how to continue here ;(

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
       Graham Norton, HRB 21284 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126