<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 5, 2013 at 12:37 PM, Nicholas Chase <span dir="ltr"><<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yeah, I think Nermina's right here; both admins and installers need the config reference, I would think -- correct me if I'm wrong -- so at the very least the parameters need to be extracted into one place to be shared by both roles.<br>
<br>
Which actually begs the question, do we want to remove all the "how to configure" information and put it in the admin guide, since we'll then also have to repeat it in the install guide?<br>
<br></blockquote><div><br></div><div>The install guide should only have a handful of adventures, not all the networking and storage use cases. Think happy path for install guide. :) <br><br></div><div>Tom's really interested in getting plain reference info - somewhat due to the word count the books are getting to, but also due to the original vision, which was reference info only in one place. He thinks admins configure and tune all the time. <br>
<br></div><div>Good discussion, thanks a bunch for poking at the ideas!<br><br></div><div>Anne<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(I know, we're back to the original question, but that is kind of the crux of the matter.)<br>
<br>
---- Nick<div class="im"><br>
<br>
On 11/5/2013 1:32 PM, Diane Fleming wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Keeping it separate is fine – I wasn't aware the config ref was for more<br>
than just the admin role.<br>
<br>
<br></div>
/Diane/<br>
/-----------------------------<u></u>-----------------/<div class="im"><br>
Diane Fleming<br>
Software Developer II - US<br>
<a href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@rackspace.com</a><br>
Cell <a href="tel:512.323.6799" value="+15123236799" target="_blank">512.323.6799</a><br>
Office <a href="tel:512.874.1260" value="+15128741260" target="_blank">512.874.1260</a><br>
Skype drfleming0227<br>
Google-plus <a href="mailto:diane.fleming@gmail.com" target="_blank">diane.fleming@gmail.com</a><br>
<br>
From: Nermina Miller <<a href="mailto:nerminamiller@gmail.com" target="_blank">nerminamiller@gmail.com</a><br></div>
<mailto:<a href="mailto:nerminamiller@gmail.com" target="_blank">nerminamiller@gmail.<u></u>com</a>>><div class="im"><br>
Date: Tuesday, November 5, 2013 12:30 PM<br>
To: Diane Fleming <<a href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@rackspace.com</a><br></div>
<mailto:<a href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@<u></u>rackspace.com</a>>><br>
Cc: Nicholas Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a> <mailto:<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>>>,<br>
"<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.<u></u>openstack.org</a><br>
<mailto:<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.<u></u>openstack.org</a>>"<br>
<<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.<u></u>openstack.org</a><br>
<mailto:<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.<u></u>openstack.org</a>>><div class="im"><br>
Subject: Re: [Openstack-docs] What's Up Doc? Special Summit Edition Nov<br>
5 2013<br>
<br>
I like the idea of having the Config Ref be a complete reference for all<br>
roles so it can be maintained in one place and referred to from other<br>
guides, but I think you have more experience with the users to be able<br>
to gauge that. - Nermina<br>
<br>
<br>
On Tue, Nov 5, 2013 at 1:22 PM, Diane Fleming<br></div><div class="im">
<<a href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@rackspace.com</a> <mailto:<a href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@<u></u>rackspace.com</a>>> wrote:<br>
<br>
Do we need two books?<br>
<br>
Can the reference tables be appendices in the Cloud Admin Guide, and<br>
rename that book "Cloud Admin Guide and Reference"?<br>
<br>
I'm fine with it either way – though it might be nice to have<br>
everything in one place given the book isn't too big.<br>
<br></div>
/Diane/<br>
/-----------------------------<u></u>-----------------/<div class="im"><br>
Diane Fleming<br>
Software Developer II - US<br></div>
<a href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@rackspace.com</a> <mailto:<a href="mailto:diane.fleming@rackspace.com" target="_blank">diane.fleming@<u></u>rackspace.com</a>><br>
Cell <a href="tel:512.323.6799" value="+15123236799" target="_blank">512.323.6799</a> <tel:<a href="tel:512.323.6799" value="+15123236799" target="_blank">512.323.6799</a>><br>
Office <a href="tel:512.874.1260" value="+15128741260" target="_blank">512.874.1260</a> <tel:<a href="tel:512.874.1260" value="+15128741260" target="_blank">512.874.1260</a>><br>
Skype drfleming0227<br>
Google-plus <a href="mailto:diane.fleming@gmail.com" target="_blank">diane.fleming@gmail.com</a> <mailto:<a href="mailto:diane.fleming@gmail.com" target="_blank">diane.fleming@gmail.<u></u>com</a>><br>
<br>
From: Nermina Miller <<a href="mailto:nerminamiller@gmail.com" target="_blank">nerminamiller@gmail.com</a><br>
<mailto:<a href="mailto:nerminamiller@gmail.com" target="_blank">nerminamiller@gmail.<u></u>com</a>>><div class="im"><br>
Date: Tuesday, November 5, 2013 12:18 PM<br></div>
To: Nicholas Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a> <mailto:<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>>><br>
Cc: "<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.<u></u>openstack.org</a><br>
<mailto:<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.<u></u>openstack.org</a>>"<br>
<<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.<u></u>openstack.org</a><br>
<mailto:<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.<u></u>openstack.org</a>>><div class="im"><br>
Subject: Re: [Openstack-docs] What's Up Doc? Special Summit Edition<br>
Nov 5 2013<br>
<br>
I just wonder what would happen if an install gal/guy needs to know<br>
how to configure something and it's in the Cloud Admin Guide instead<br>
of Config Ref. - Nermina<br>
<br>
<br>
On Tue, Nov 5, 2013 at 1:10 PM, Nicholas Chase <<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a><br></div><div class="im">
<mailto:<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>>> wrote:<br>
<br>
<br>
<br>
On 11/5/2013 12:37 PM, Anne Gentle wrote:<br>
<br>
<br>
<br>
<br>
On Tue, Nov 5, 2013 at 10:02 AM, Nicholas Chase<br>
<<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a> <mailto:<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>><br></div>
<mailto:<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a> <mailto:<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>>>><div><div class="h5">
<br>
wrote:<br>
<br>
Restructure:<br>
Despite the tradeoff that we have to re-communicate<br>
some more<br>
moves to<br>
all the teams, we want to trim the configuration<br>
reference down<br>
to just<br>
listings of options, no how-to or explanatory<br>
information. Move this<br>
type of info to the Cloud Admin Guide. Are we good<br>
with this<br>
plan for<br>
Icehouse?<br>
<br>
<br>
Are you suggesting that the Config References just<br>
lists parameters<br>
without any explanation of what they mean? I agree<br>
with eliminating<br>
conceptual or how-to information and moving it to cloud<br>
admin, but<br>
I'm against removing explanations of what the<br>
parameters mean/do.<br>
<br>
<br>
No, it'll be a book with just xi:includes of the current<br>
tables. What do<br>
you think?<br>
<br>
<br>
That makes more sense, as long as it's convenient (read:<br>
reasonably intuitive) to find the additional information for<br>
those who will need it, regardless of their function.<br>
<br>
<br>
---- Nick<br>
<br></div></div>
______________________________<u></u>___________________<br>
Openstack-docs mailing list<br>
Openstack-docs@lists.__<a href="http://openstack.org" target="_blank">opensta<u></u>ck.org</a><br>
<mailto:<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.<u></u>openstack.org</a>><br>
<a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-docs" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-docs</a><div class="im"><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-docs</a>><br>
<br>
<br>
<br>
<br>
--<br>
Thank you!<br>
<br>
Nermina Miller<br>
Tech Writer and Editor<br>
<br>
<br>
<br>
<br>
--<br>
Thank you!<br>
<br>
Nermina Miller<br>
Tech Writer and Editor<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>_________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.<u></u>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-docs</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div></div>