<div dir="ltr">No problem, Summer. Would be happy too! Is all of the info included in the initial email? Thanks! - Nermina</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 8, 2013 at 6:25 PM, Summer Long <span dir="ltr"><<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Interesting, Anne, that closely matches what I put together for the
Red Hat general introduction (included in all the guides so far). I
like the additional 'why cloud' and 'logical architecture' sections.
<br>
<br>
Question, is that only included in the Installation Guide? I'd sent
our introduction over to Shaun McCance, via Tom, for review towards
possibly including in all intro-type docs. Obviously, that doesn't
need to be done if the Getting Started intro can be used across
other docs.<br>
<br>
Nermina, are you ok with coming up with a distribution-dependant
table, in case that's necessary (per Tom, sounds like it is)?<br>
<br>
:><div class="im"><br>
Summer<br>
<br>
<br>
<div>
<div><font color="#666666">Summer Long<br>
OpenStack Documentation<br>
Engineering Content Services<br>
<br>
Red Hat Asia Pacific<br>
Brisbane, Australia</font><br>
<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a></div>
</div>
<br>
</div><div><div class="h5"><span style>
<div>On 08/09/2013 01:14 AM, Nermina
Miller wrote:<br>
</div>
</span>
<blockquote type="cite">
<div dir="ltr">No problem, then ;)</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Aug 8, 2013 at 11:08 AM, Anne
Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Sure, but realize that with git-based work,
it merges in, and if it can't resolve the merge, a human
makes sure it all works together still. So we don't have
to "lock" any given file. Which to me is full of win!
<div>
<br>
</div>
<div>Anne</div>
</div>
<div class="gmail_extra">
<div>
<div><br>
<br>
<div class="gmail_quote">On Thu, Aug 8, 2013 at 10:06
AM, Nermina Miller <span dir="ltr"><<a href="mailto:nerminamiller@gmail.com" target="_blank">nerminamiller@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Anne and Summer,
<div><br>
</div>
<div>Since I'm working on the rewrite of Getting
Started, should we wait till that process is
done to make these edits? I have Mirantis SMEs
looking at it and I'm updating simultaneously.</div>
<div><br>
</div>
<div>Thank you both!</div>
<div><br>
</div>
<div>Nermina</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div>On Thu, Aug 8, 2013 at 9:00 AM, Anne
Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span>
wrote:<br>
</div>
<div>
<div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">A while back I fixed this
bug:
<div><a href="https://bugs.launchpad.net/openstack-manuals/+bug/1160757" target="_blank">https://bugs.launchpad.net/openstack-manuals/+bug/1160757</a><br>
</div>
<div>with this patch:</div>
<div><a href="https://review.openstack.org/#/c/26950/3/doc/src/docbkx/common/getstart.xml" target="_blank">https://review.openstack.org/#/c/26950/3/doc/src/docbkx/common/getstart.xml</a><br>
</div>
<div>Which offered a lot more
explanation of services, daemons,
and so forth. The file I updated is
common/getstart.xml. I think this
info can go there. Since it's reused
many places, do not use conditional
markup in that file. </div>
<div><br>
</div>
<div>Anne</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div>
<div>On Wed, Aug 7, 2013 at 7:14
PM, Summer Long <span dir="ltr"><<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div text="#000000" bgcolor="#FFFFFF"> Hi Tom,<br>
Yes, I can see your point.
Am just thinking about
whether folks will find it
if they are not in the
middle of an OpenStack
install? <br>
<br>
Are all of the values really
distribution dependant? If
so, and if the installation
really is the better place,
then putting them into
distribution Installation
guides probably would work
better. <br>
<br>
Other opinions?<br>
<br>
cheers, Summer<br>
<br>
<div>
<div><font color="#666666">Summer
Long<br>
OpenStack
Documentation<br>
Engineering Content
Services<br>
<br>
Red Hat Asia Pacific<br>
Brisbane, Australia</font><br>
<a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a></div>
</div>
<br>
<span>
<div>On 08/08/2013 09:58
AM, Tom Fifield wrote:<br>
</div>
</span>
<blockquote type="cite">
<pre>Hmm, nice one!
My initial impression is that this information is most useful to users
on installation (planning systems), rather than post-install
'fixing'/configuration.
It's also raised some interesting questions in my mind about whether the
configuration reference is distribution agnostic - since uid/gids are
different between RHEL and ubuntu if I remember correctly. My feeling is
that to be more low maintenance (which was one of the driving factors in
the creation of the config reference), we probably want it to be "just
about OpenStack", rather than doing conditional formatting for
rhel/ubuntu/suse etc. However, I also have the feeling that we'll end up
with more of these situations and I'll break down :)
Can we move this discussion to the mailing list?
Regards,
Tom
On 08/08/13 07:22, Summer Long wrote:
</pre>
<blockquote type="cite">
<pre>Hi Tom,
I just got a request to put the reserved uids/guids used by OpenStack
somewhere in the documentation. So that configurers can know what
products pull in which uid/gids/software, and also in case they are
assigning uids/gids to other third-party software or systems.
It feels like the Configuration Reference is the right place. Have you
had any requests for these?
For example:
keystone:x:163:163:OpenStack Keystone Daemons:/var/lib/keystone:sbin/nologin
glance:x:161:161:OpenStack Glance Daemons:/var/lib/glance:/sbin/nologin
cinder:x:165:165:OpenStack Cinder Daemons:/var/lib/cinder:/sbin/nologin
nova:x:162:162:OpenStack Nova Daemons:/var/lib/nova:/sbin/nologin
Plus neutron, swift, ceilometer, heat?
And if we're including info for third-party glue, then possibly:
mysql:x:27:27:MySQL Server:/var/lib/mysql:/bin/bash
qpidd:x:498:499:Owner of Qpidd Daemons:/var/lib/qpidd:/sbin/nologin
nagios:x:496:495::/var/spool/nagios:/sbin/nologin
What do you think?
thanks, Summer
--
Summer Long
OpenStack Documentation
Engineering Content Services
Red Hat Asia Pacific
Brisbane, Australia
<span><font color="#888888"><a href="mailto:slong@redhat.com" target="_blank">slong@redhat.com</a> <a href="mailto:slong@redhat.com" target="_blank"><mailto:slong@redhat.com></a>
</font></span></pre>
<span><font color="#888888"> </font></span></blockquote>
<span><font color="#888888"> </font></span></blockquote>
<br>
</div>
<br>
</div>
</div>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">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>
</blockquote>
</div>
<span><font color="#888888"><br>
<br clear="all">
<div><br>
</div>
-- <br>
Anne Gentle<br>
<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</font></span></div>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">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>
</blockquote>
</div>
</div>
</div>
<span><font color="#888888"><br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Thank you!
<div><br>
</div>
<div>Nermina Miller</div>
<div>Tech Writer and Editor</div>
</div>
</font></span></div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
</div>
</div>
<span><font color="#888888">-- <br>
Anne Gentle<br>
<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</font></span></div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Thank you!
<div><br>
</div>
<div>Nermina Miller</div>
<div>Tech Writer and Editor</div>
</div>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Thank you!<div><br></div><div>Nermina Miller</div><div>Tech Writer and Editor</div></div>
</div>