<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 18, 2015 at 6:15 PM, Bernd Bausch <span dir="ltr"><<a href="mailto:berndbausch@gmail.com" target="_blank">berndbausch@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi everybody,<br>
<br>
while I mean to look at the Debian documentation bugs (I believe I have<br>
confirmed one or two by now), I am busy this week with other activities.<br>
Should there be no progress otherwise, I would be very happy to concentrate<br>
on them again next week - confirming, perhaps also fixing them, once I<br>
understand how to do that.<br>
<br>
Since you have never heard of me, a short self-introduction: As an<br>
independent IT instructor, I have been teaching three-days courses named<br>
"Openstack Fundamentals" for about half a year now (this week again). When I<br>
started learning about Openstack, I was overwhelmed first but thanks to the<br>
installation guides finally managed to navigate through this fascinating<br>
technology. It would be great if I could contribute a little to improving<br>
them and other guides to newcomers.<br>
I am located in Tokyo and look forward to meeting some of you at the summit<br>
in November.<br>
<br></blockquote><div><br></div><div>Thanks for introducing yourself Bernd, and welcome! Really appreciate your interest and this is a great place to start.</div><div><br></div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bernd<br>
<br>
Bernd Bausch<br>
<a href="mailto:berndbausch@gmail.com">berndbausch@gmail.com</a><br>
<a href="tel:%2B81%2080%208892%205564" value="+818088925564">+81 80 8892 5564</a><br>
<br>
<br>
-----Original Message-----<br>
<br>
Date: Wed, 18 Feb 2015 09:37:41 -0600<br>
From: Anne Gentle <<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>><br>
To: Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>><br>
Cc: "<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>"<br>
<<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>>, Thomas Goirand<br>
<<a href="mailto:thomas@goirand.fr">thomas@goirand.fr</a>><br>
Subject: Re: [OpenStack-docs] Results from installation of OpenStack<br>
on Debian<br>
Message-ID:<br>
<CAD0KtVH-05fHrEX+d2iEewu601ACNY-YF-hNar5G=<a href="mailto:RSVUftw6g@mail.gmail.com">RSVUftw6g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Fri, Feb 6, 2015 at 12:16 PM, Anne Gentle <<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>><br>
wrote:<br>
<br>
> Hi again all,<br>
> I'm top posting, sorry. I finally had a chance to do more in-depth<br>
> analysis of these bug reports.<br>
><br>
> I hesitated initially on whether to post to the list, since there are a<br>
> lot of hard feelings coming up around this, and people are pretty tired of<br>
> the "drama." But we need to address these issues, and I don't want anyone<br>
> to feel personally tied to the issues. There is no individual blame or<br>
> fault here. That said, as PTL I do need to make a decision based on<br>
> technical merits.<br>
><br>
> I did an analysis to see whether the install issues come up from a<br>
> difference in philosophy or bugs in the doc. I'm leaning towards "bugs in<br>
> the doc causing issues" as the final analysis, and I'd like us to consider<br>
> stopping links to the Debian Install Guide until the issues are addressed.<br>
><br>
> Here's my analysis.<br>
><br>
> Where debconf inconsistency that don't cause failure to install but may<br>
> confuse, these I don't consider as reasons to stop publishing:<br>
> 1. deprecated options in mysql conf<br>
> 2. database names end in db<br>
> 3. uses ip address instead of name<br>
> 4. admin tenant and user instead of separate users and a service tenant<br>
> 5. deprecated xml body middleware and kvs backend for keystone<br>
> 6. debconf doesn't enable verbose logging<br>
><br>
> Where there are actual doc bugs due to Debian being different, causing<br>
> problems later:<br>
> 1. rabbitmq bound to 127.0.0.1, perhaps means it thinks of itself as a<br>
> single node install. While this is a philosophical difference, it<br>
> does prevent services on the network and compute nodes from accessing the<br>
> queue.<br>
> 2. glance.conf problem that causes actual warnings [keystone_authtoken]:<br>
> identity_uri must not use localhost<br>
> 3. glance.conf problem that causes actual warnings [keystone_authtoken]:<br>
> auth_uri must be set to public url, clients may not be able to<br>
authenticate<br>
> against an admin endpoint<br>
> 4. glance.conf problem: default_store in wrong location, should be in<br>
> [glance_store]<br>
> 5. my_ip incorrectly configured for glance, causing inability to connect<br>
> from a separate server (When launching an instance, Compute attempts to<br>
> contact the image service using the value of the my_ip option). Again this<br>
> is probably due to assuming a single server install.<br>
><br>
> nova.conf config:<br>
> (opinion) metadata service enabled, different from other distros<br>
> 6. spice console won't work<br>
> 7. [keystone_authtoken]: identity_uri must not use localhost<br>
> 8. [keystone_authtoken]: auth_uri must be set to public url<br>
> 9.doesn't reference controller node for nova to glance connection (acts<br>
> like single node install)<br>
> 10.problems with needing port 35357 instead of 5000<br>
> (opinion) nova.conf compute node could remove database connection but<br>
> optional<br>
><br>
> neutron problems<br>
> (opinion, but may cause problems) doesn't let people choose their own<br>
> network settings<br>
> 11. uses deprecated config files<br>
> 12. local_ip option not there<br>
> 13. metadata agent won't connect to misconfigured database<br>
> 14. 16. same keystone problems as nova and glance<br>
> 15. L2 population won't work<br>
><br>
> Overall problems due to basic architecture decisions being different:<br>
> - Debian assumes images served from same node as compute node<br>
> - Debian doesn't have nova-network<br>
> - Debian assumes use of Open vSwitch<br>
> - Debian assumes certain networking settings<br>
> - Debian enables rabbitmq for glance prior to needing it since telemetry<br>
> is optional, so architecture seems to assume telemetry is a requirement.<br>
><br>
> I have been mediating this debate since November 2014 so I'd like to get<br>
> forward movement. My analysis indicates the issues are due to too many<br>
> assumptions being made for Debian causing problems. I know Thomas and Alex<br>
> planned to test this week, so I hope they can validate these bugs and<br>
> devise a plan to address them.<br>
><br>
> Based on the plan, we'll make a decision about links and/or redirects.<br>
><br>
> Let me know the plans by replying here or responding to the bugs by<br>
> 2/16/15.<br>
><br>
<br>
Looks like there is some bug triaging going on, but I haven't heard a plan<br>
and at last week's Doc Team meeting Alex Adamov said he could work on the<br>
plan and have it to us by Monday 2/16. [1] How's that going?<br>
<br>
I've proposed a patch that removes the Debian guide from the landing page<br>
in the meantime while we await the plan. [2]<br>
Anne<br>
<br>
1.<br>
<a href="http://eavesdrop.openstack.org/meetings/docteam/2015/docteam.2015-02-11-14.0
0.html" target="_blank">http://eavesdrop.openstack.org/meetings/docteam/2015/docteam.2015-02-11-14.0<br>
0.html</a><br>
2. <a href="https://review.openstack.org/157037" target="_blank">https://review.openstack.org/157037</a><br>
<br>
<br>
><br>
> Thanks,<br>
> Anne<br>
><br>
> On Mon, Feb 2, 2015 at 4:38 PM, Anne Gentle <<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a><br>
> > wrote:<br>
><br>
>><br>
>><br>
>> On Mon, Feb 2, 2015 at 3:21 PM, Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>><br>
>> wrote:<br>
>><br>
>>> Over the weekend, I attempted to install OpenStack Juno core services<br>
>>> (keystone, glance, nova, and neutron) on Debian Wheezy using the Juno<br>
>>> installation guide. I could not obtain an operational environment (i.e.,<br>
>>> successfully launch an instance) by exclusively using configuration<br>
>>> generated by Debconf (and associated tools) or after fixing/augmenting<br>
the<br>
>>> configuration with existing manual steps in the guide (primarily<br>
networking<br>
>>> content). I opened the following bugs describing my observations:<br>
>>><br>
>>> <a href="http://tinyurl.com/ooccchh" target="_blank">http://tinyurl.com/ooccchh</a><br>
>>><br>
>>> Thomas (zigo) and I briefly discussed a few of these issues on IRC, but<br>
>>> I'm documenting them all for tracking purposes.<br>
>>><br>
>><br>
>> Okay, thanks for the list Matt. Looks like 14 new bugs, some of which<br>
>> can't really be fixed in the docs, at a glance. The bug reports are<br>
>> thorough, and I would like further investigation.<br>
>><br>
>> Thomas and Alex and anyone else who'd like to work on these: Our usual<br>
>> processes, with these new bugs, is to look at them, mark them<br>
>> Status:Confirmed if you agree it can be fixed in the docs, or if it needs<br>
>> to be fixed in packaging and/or the config tool, then please set to<br>
>> Status:Won't Fix. I believe they are all of Medium Importance.<br>
>><br>
>> You can also assign yourself to these bugs once they are Status:Confirmed<br>
>> by clicking the exclamation point next to "Unassigned" in the Assigned<br>
>> column and then click "Pick me."<br>
>><br>
>><br>
>>><br>
>>> I'm stepping away to focus on the networking guide content.<br>
>>><br>
>><br>
>> Sounds fine, we'll keep up with reviews of the Install Guide.<br>
>><br>
>> Thanks,<br>
>> Anne<br>
>><br>
>><br>
>>><br>
>>> _______________________________________________<br>
>>> OpenStack-docs mailing list<br>
>>> <a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
>>><br>
>>><br>
>><br>
>><br>
>> --<br>
>> Anne Gentle<br>
>> <a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> Anne Gentle<br>
> <a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a><br>
><br>
<br>
<br>
<br>
--<br>
Anne Gentle<br>
<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://lists.openstack.org/pipermail/openstack-docs/attachments/20150218/fc
fa67e9/attachment.html" target="_blank">http://lists.openstack.org/pipermail/openstack-docs/attachments/20150218/fc<br>
fa67e9/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br>
<br>
End of OpenStack-docs Digest, Vol 32, Issue 23<br>
**********************************************<br>
<br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a></div>
</div></div>