<div dir="ltr">Heh.<div><br></div><div>Okay, I don't see the value in changing all of our source at this point. Here's an example though.</div><div><br></div><div>This example of literal markup shows an inline "code" (ok, weak example) marking. The nova user is not an option, but we do want to set it off as it's the name we expect.</div><div><br></div><div><div><para>Replace <replaceable>NOVA_PASS</replaceable> with the password you chose for the <literal>nova</literal> user in the Identity service.</para></div><div><br></div><div>In the example below, if we would use <option> instead of <literal> we could one day automate a list of options described in the install guide:</div><div><br></div><div><note><para>Comment out any <literal>auth_host</literal>, <literal>auth_port</literal>, and <literal>auth_protocol</literal> options because the <literal>identity_uri</literal> option replaces them.</para></note></div></div><div><br></div><div>I really don't think the difference is worth the trouble in changing the current source though.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 17, 2014 at 11:00 AM, Matt Kassawara <span dir="ltr"><<a href="mailto:mkassawara@gmail.com" target="_blank">mkassawara@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">That... did not help me.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 17, 2014 at 10:54 AM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Sep 17, 2014 at 8:46 AM, Matt Kassawara <span dir="ltr"><<a href="mailto:mkassawara@gmail.com" target="_blank">mkassawara@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Do we also prefer <option> over <literal> for them?</div></blockquote><div><br></div></span><div><option> is markup for inline options</div><div><a href="https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Configuration_options_.28inline.29" target="_blank">https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Configuration_options_.28inline.29</a><br></div><div><br></div><div><literal> is markup for inline code</div><div><a href="https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Code_or_data_.28inline.29" target="_blank">https://wiki.openstack.org/wiki/Documentation/DocBook_conventions#Code_or_data_.28inline.29</a><br></div><div><br></div><div>Using <option> in this way would theoretically let us generate options tables or pull out in other ways.</div><div><div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 17, 2014 at 8:06 AM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Sep 17, 2014 at 4:36 AM, Andreas Jaeger <span dir="ltr"><<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Reviewing<br>
<a href="https://review.openstack.org/#/c/122027/" target="_blank">https://review.openstack.org/#/c/122027/</a><br>
<br>
I noticed the usage of "key" but I see "option" used in other guides<br>
when changing configuration files.<br>
<br>
Example:<br>
1) "Set auth_uri key to..."<br>
2) "Set auth_uri option to..."<br>
<br>
Is there a preferred way or is this something we use interchangeable?<br>
<span><font color="#888888"><br></font></span></blockquote><div><br></div></span><div>I'd prefer we stick to the option term consistently (even if it's a key that goes into that option). </div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span><font color="#888888">
Andreas<br>
--<br>
Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter: jaegerandi<br>
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>
<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>
</font></span></blockquote></span></div><br></div></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><br></div>
</div></div></blockquote></div></div></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>