openstack/openstack-manuals
Code Issues Proposed changes

Merge "Removes references to Launchpad Answers and replaces"

Browse Source
This commit is contained in:
Jenkins
2013-04-05 04:15:56 +00:00
committed by Gerrit Code Review
parent d444b2d554 4b1dc15281
commit 3589d524d3
3 changed files with 192 additions and 179 deletions
Download Patch File Download Diff File Expand all files Collapse all files

94
doc/src/docbkx/common/support-compute.xml
View File

@@ -14,27 +14,81 @@
<para>You have two options for logging for OpenStack Compute based on configuration
settings. In nova.conf, include the logfile option to enable logging. Alternatively
you can set use_syslog=1, and then the nova daemon logs to syslog.</para></section>
<section xml:id="common-errors-and-fixes-for-openstack-compute">
<title>Common Errors and Fixes for OpenStack Compute</title>
<para>The Launchpad Answers site offers a place to ask and answer questions, and you can also mark questions as frequently asked questions. This section describes some errors people have posted to Launchpad Answers and IRC. We are constantly fixing bugs, so online resources are a great way to get the most up-to-date errors and fixes.</para>
<section xml:id="common-errors-and-fixes-for-openstack-compute">
<title>Common Errors and Fixes for OpenStack Compute</title>
<para>The ask.openstack.org site offers a place to ask and
answer questions, and you can also mark questions as
frequently asked questions. This section describes some
errors people have posted previously. We
are constantly fixing bugs, so online resources are a
great way to get the most up-to-date errors and
fixes.</para>
<para>Credential errors, 401, 403 forbidden errors</para>
<para>A 403 forbidden error is caused by missing credentials. Through current installation methods, there are basically two ways to get the novarc file. The manual method requires getting it from within a project zipfile, and the scripted method just generates novarc out of the project zip file and sources it for you. If you do the manual method through a zip file, then the following novarc alone, you end up losing the creds that are tied to the user you created with nova-manage in the steps before.</para>
<para>When you run nova-api the first time, it generates the certificate authority information, including openssl.cnf. If it gets started out of order, you may not be able to create your zip file. Once your CA information is available, you should be able to go back to nova-manage to create your zipfile. </para><para>You may also need to check your proxy settings to see if they are causing problems with the novarc creation.</para>
<para>Instance errors</para>
<para>Sometimes a particular instance shows "pending" or you cannot SSH to it. Sometimes the image itself is the problem. For example, when using flat manager networking, you do not have a dhcp server, and an ami-tiny image doesn't support interface injection so you cannot connect to it. The fix for this type of problem is to use an Ubuntu image, which should obtain an IP address correctly with FlatManager network settings. To troubleshoot other possible problems with an instance, such as one that stays in a spawning state, first check your instances directory for i-ze0bnh1q dir to make sure it has the following files:</para>
<itemizedlist><listitem><para>libvirt.xml</para></listitem>
<listitem><para>disk</para></listitem>
<listitem><para>disk-raw</para></listitem>
<listitem><para>kernel</para></listitem>
<listitem><para>ramdisk</para></listitem>
<listitem><para>console.log (Once the instance actually starts you should see a console.log.)</para></listitem>
</itemizedlist>
<para>Check the file sizes to see if they are reasonable. If any are missing/zero/very small then nova-compute has somehow not completed download of the images from objectstore. </para>
<para>Also check nova-compute.log for exceptions. Sometimes they don't show up in the
console output. </para><para>
Next, check the /var/log/libvirt/qemu/i-ze0bnh1q.log file to see if it exists and has any useful error messages in it.</para>
<para>Finally, from the instances/i-ze0bnh1q directory, try <code>virsh create libvirt.xml</code> and see if you get an error there.</para>
<para>A 403 forbidden error is caused by missing credentials.
Through current installation methods, there are basically
two ways to get the novarc file. The manual method
requires getting it from within a project zipfile, and the
scripted method just generates novarc out of the project
zip file and sources it for you. If you do the manual
method through a zip file, then the following novarc
alone, you end up losing the creds that are tied to the
user you created with nova-manage in the steps
before.</para>
<para>When you run nova-api the first time, it generates the
certificate authority information, including openssl.cnf.
If it gets started out of order, you may not be able to
create your zip file. Once your CA information is
available, you should be able to go back to nova-manage to
create your zipfile. </para>
<para>You may also need to check your proxy settings to see if
they are causing problems with the novarc creation.</para>
<para>Instance errors</para>
<para>Sometimes a particular instance shows "pending" or you
cannot SSH to it. Sometimes the image itself is the
problem. For example, when using flat manager networking,
you do not have a dhcp server, and an ami-tiny image
doesn't support interface injection so you cannot connect
to it. The fix for this type of problem is to use an
Ubuntu image, which should obtain an IP address correctly
with FlatManager network settings. To troubleshoot other
possible problems with an instance, such as one that stays
in a spawning state, first check your instances directory
for i-ze0bnh1q dir to make sure it has the following
files:</para>
<itemizedlist>
<listitem>
<para>libvirt.xml</para>
</listitem>
<listitem>
<para>disk</para>
</listitem>
<listitem>
<para>disk-raw</para>
</listitem>
<listitem>
<para>kernel</para>
</listitem>
<listitem>
<para>ramdisk</para>
</listitem>
<listitem>
<para>console.log (Once the instance actually starts
you should see a console.log.)</para>
</listitem>
</itemizedlist>
<para>Check the file sizes to see if they are reasonable. If
any are missing/zero/very small then nova-compute has
somehow not completed download of the images from
objectstore. </para>
<para>Also check nova-compute.log for exceptions. Sometimes
they don't show up in the console output. </para>
<para> Next, check the /var/log/libvirt/qemu/i-ze0bnh1q.log
file to see if it exists and has any useful error messages
in it.</para>
<para>Finally, from the instances/i-ze0bnh1q directory, try
<code>virsh create libvirt.xml</code> and see if you
get an error there.</para>
</section>
<section xml:id="reset-state">
<title>Manually reset the state of an instance</title>

118
doc/src/docbkx/common/support.xml
View File

@@ -7,47 +7,42 @@
<para>Online resources aid in supporting OpenStack and the community members are willing and able to answer questions and help with bug suspicions. We are constantly improving and adding to the main features of OpenStack, but if you have any problems, do not hesitate to ask. Here are some ideas for supporting OpenStack and troubleshooting your existing installations.</para>
<section xml:id="community-support">
<title>Community Support</title> <para>Here are some places you can locate others who want to help.</para>
<simplesect><title>The Launchpad Answers area</title>
<para>During setup or testing, you may have questions about how to do something, or end up in
a situation where you can't seem to get a feature to work correctly. One place to
look for help is the Answers section on Launchpad. Launchpad is the "home" for the
project code and its developers and thus is a natural place to ask about the
project. When visiting the Answers section, it is usually good to at least scan over
recently asked questions to see if your question has already been answered. If that
is not the case, then proceed to adding a new question. Be sure you give a clear,
concise summary in the title and provide as much detail as possible in the
description. Paste in your command output or stack traces, link to screenshots, and
so on. The Launchpad Answers areas are available here: </para>
<itemizedlist>
<listitem><para> OpenStack Compute: <link
xlink:href="https://answers.launchpad.net/nova"
>https://answers.launchpad.net/nova</link></para></listitem>
<listitem><para> OpenStack Object Storage: <link
xlink:href="https://answers.launchpad.net/swift"
>https://answers.launchpad.net/swift</link></para></listitem>
<listitem><para> OpenStack Image Delivery and Registration: <link
xlink:href="https://answers.launchpad.net/glance"
>https://answers.launchpad.net/glance</link></para></listitem>
<listitem><para> OpenStack Identity: <link
xlink:href="https://answers.launchpad.net/keystone"
>https://answers.launchpad.net/keystone</link></para></listitem>
<listitem><para> OpenStack Dashboard: <link
xlink:href="https://answers.launchpad.net/horizon"
>https://answers.launchpad.net/horizon</link></para></listitem>
<listitem><para> OpenStack Network Connectivity: <link
xlink:href="https://answers.launchpad.net/quantum"
>https://answers.launchpad.net/quantum</link></para></listitem>
</itemizedlist>
</simplesect>
<simplesect><title>OpenStack mailing list</title>
<para>Posting your question or scenario to the OpenStack mailing list is a great way to get
answers and insights. You can learn from and help others who may have the same
scenario as you. Go to <link xlink:href="https://launchpad.net/~openstack"
>https://launchpad.net/~openstack</link> and click "Subscribe to mailing list"
or view the archives at <link xlink:href="https://lists.launchpad.net/openstack/"
>https://lists.launchpad.net/openstack/</link>. You may be interested in the other
mailing lists for specific projects or development - these can be found
<link xlink:href="http://wiki.openstack.org/MailingLists">on the wiki</link>. </para></simplesect><simplesect>
<simplesect>
<title>ask.openstack.org</title>
<para>During setup or testing, you may have questions
about how to do something, or end up in a situation
where you can't seem to get a feature to work
correctly. The ask.openstack.org site is available for
questions and answers. When visiting the Ask site at
<link xlink:href="http://ask.openstack.org"
>http://ask.openstack.org</link>, it is usually
good to at least scan over recently asked questions to
see if your question has already been answered. If
that is not the case, then proceed to adding a new
question. Be sure you give a clear, concise summary in
the title and provide as much detail as possible in
the description. Paste in your command output or stack
traces, link to screenshots, and so on. </para>
</simplesect>
<simplesect><title>OpenStack mailing lists</title>
<para>Posting your question or scenario to the OpenStack
mailing list is a great way to get answers and
insights. You can learn from and help others who may
have the same scenario as you. Go to <link
xlink:href="https://launchpad.net/~openstack"
>https://launchpad.net/~openstack</link> and click
"Subscribe to mailing list" or view the archives at
<link
xlink:href="https://lists.launchpad.net/openstack/"
>https://lists.launchpad.net/openstack/</link>.
You may be interested in the other mailing lists for
specific projects or development - these can be found
<link
xlink:href="http://wiki.openstack.org/MailingLists"
>on the wiki</link>. A description of all the
additional mailing lists is available at
<link
xlink:href="http://wiki.openstack.org/MailingLists">http://wiki.openstack.org/MailingLists</link>.</para></simplesect><simplesect>
<title>The OpenStack Wiki search </title>
<para>The <link xlink:href="http://wiki.openstack.org/">OpenStack wiki</link> contains content
on a broad range of topics, but some of it sits a bit below the surface. Fortunately, the wiki
@@ -73,11 +68,10 @@
<listitem><para>Be sure to include what version of the software you are using.
This is especially critical if you are using a development branch eg. "Grizzly
release" vs git commit bc79c3ecc55929bac585d04a03475b72e06a3208. </para></listitem>
<listitem><para>Any deployment specific info is helpful as well. eg.
Ubuntu 12.04, multi-node install.</para></listitem> </itemizedlist>
<listitem><para>Any deployment specific info is helpful as well, such as Ubuntu
12.04, multi-node install.</para></listitem> </itemizedlist>
<para>The Launchpad Bugs areas are available here - OpenStack Compute:
</para>
<para>The Launchpad Bugs areas are available here - : </para>
<itemizedlist>
<listitem><para> OpenStack Compute: <link
xlink:href="https://bugs.launchpad.net/nova"
@@ -100,17 +94,27 @@
</itemizedlist>
</simplesect>
<simplesect><title>The OpenStack IRC channel </title>
<para>The OpenStack community lives and breathes in the #openstack IRC channel on the
Freenode network. You can come by to hang out, ask questions, or get immediate
feedback for urgent and pressing issues. To get into the IRC channel you need to
install an IRC client or use a browser-based client by going to
http://webchat.freenode.net/. You can also use Colloquy (Mac OS X,
http://colloquy.info/) or mIRC (Windows, http://www.mirc.com/) or XChat (Linux).
When you are in the IRC channel and want to share code or command output, the
generally accepted method is to use a Paste Bin, the OpenStack project has one at
http://paste.openstack.org. Just paste your longer amounts of text or logs in the
web form and you get a URL you can then paste into the channel. The OpenStack IRC
channel is: #openstack on irc.freenode.net. </para></simplesect>
<simplesect>
<title>The OpenStack IRC channel </title>
<para>The OpenStack community lives and breathes in the
#openstack IRC channel on the Freenode network. You
can come by to hang out, ask questions, or get
immediate feedback for urgent and pressing issues. To
get into the IRC channel you need to install an IRC
client or use a browser-based client by going to
http://webchat.freenode.net/. You can also use
Colloquy (Mac OS X, http://colloquy.info/) or mIRC
(Windows, http://www.mirc.com/) or XChat (Linux). When
you are in the IRC channel and want to share code or
command output, the generally accepted method is to
use a Paste Bin, the OpenStack project has one at
http://paste.openstack.org. Just paste your longer
amounts of text or logs in the web form and you get a
URL you can then paste into the channel. The OpenStack
IRC channel is: #openstack on irc.freenode.net. A list
of all the OpenStack-related IRC channels is at <link
xlink:href="https://wiki.openstack.org/wiki/IRC"
>https://wiki.openstack.org/wiki/IRC</link>.</para>
</simplesect>
</section>
</chapter>

159
doc/src/docbkx/openstack-ops/src/ch_ops_upstream.xml
View File

@@ -29,55 +29,10 @@
the section below or use one of the channels for support
below.</para>
<para>Your first port of call should be the official OpenStack
documentation, found on http://docs.openstack.org</para>
<para>You can get questions answered on the Launchpad site for
each project:</para>
<itemizedlist>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
xlink:href="https://answers.launchpad.net/nova"
>Nova Q&amp;A</link> (https://answers.launchpad.net/nova)</para>
</listitem>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
xlink:href="https://answers.launchpad.net/swift"
>Swift Q&amp;A</link> (https://answers.launchpad.net/swift)</para>
</listitem>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
xlink:href="https://answers.launchpad.net/glance"
>Glance Q&amp;A</link> (https://answers.launchpad.net/glance)</para>
</listitem>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
xlink:href="https://answers.launchpad.net/keystone"
>Keystone Q&amp;A</link> (https://answers.launchpad.net/keystone)</para>
</listitem>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
xlink:href="https://answers.launchpad.net/quantum"
>Quantum Q&amp;A</link> (https://answers.launchpad.net/quantum)</para>
</listitem>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
xlink:href="https://answers.launchpad.net/cinder"
>Cinder Q&amp;A</link> (https://answers.launchpad.net/cinder)</para>
</listitem>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
xlink:href="https://answers.launchpad.net/horizon"
>Horizon Q&amp;A</link> (https://answers.launchpad.net/horizon)</para>
</listitem>
</itemizedlist>
documentation, found on http://docs.openstack.org.</para>
<para>You can get questions answered on the ask.openstack.org site.</para>
<para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/Mailing_Lists"
>Mailing
Lists</link> (https://wiki.openstack.org/wiki/Mailing_Lists)
@@ -87,7 +42,7 @@
<itemizedlist>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://launchpad.net/~openstack"
>General
list</link>: <code>openstack@lists.launchpad.net</code>.
@@ -97,7 +52,7 @@
</listitem>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
>Operators
list</link>: <code>openstack-operators@lists.openstack.org.</code>
@@ -108,7 +63,7 @@
</listitem>
<listitem>
<para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
>Development
list</link>: <code>openstack-dev@lists.openstack.org</code>.
@@ -124,7 +79,7 @@
wiki page where you can search through the
discussions.</para>
<para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/IRC"
>Multiple IRC
channels</link> (https://wiki.openstack.org/wiki/IRC) are
@@ -141,7 +96,7 @@
essential to learn how to easily submit a bug
report.</para>
<para>All OpenStack projects use <link
xlink:title="OpenStack Wiki"
xlink:href="http://launchpad.net/"
>Launchpad</link> for bug tracking. You'll need to create
an account on Launchpad before you can submit a bug
@@ -155,96 +110,96 @@
<itemizedlist>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/nova/+filebug"
>Nova</link> (https://bugs.launchpad.net/nova/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/python-novaclient/+filebug"
>python-novaclient</link> (https://bugs.launchpad.net/python-novaclient/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/swift/+filebug"
>Swift</link> (https://bugs.launchpad.net/swift/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/python-swiftclient/+filebug"
>python-swiftclient</link>
(https://bugs.launchpad.net/python-swiftclient/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/glance/+filebug"
>Glance</link> (https://bugs.launchpad.net/glance/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/python-glanceclient/+filebug"
>python-glanceclient</link>
(https://bugs.launchpad.net/python-glanceclient/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/keystone/+filebug"
>Keystone</link> (https://bugs.launchpad.net/keystone/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/python-keystoneclient/+filebug"
>python-keystoneclient</link>
(https://bugs.launchpad.net/python-keystoneclient/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/quantum/+filebug"
>Quantum</link> (https://bugs.launchpad.net/quantum/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/python-quantumclient/+filebug"
>python-quantumclient</link>
(https://bugs.launchpad.net/python-quantumclient/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/cinder/+filebug"
>Cinder</link> (https://bugs.launchpad.net/cinder/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/python-cinderclient/+filebug"
>python-cinderclient</link>
(https://bugs.launchpad.net/python-cinderclient/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug in <link
xlink:title="OpenStack Wiki"
xlink:href="https://bugs.launchpad.net/horizon/+filebug"
>Horizon</link> (https://bugs.launchpad.net/horizon/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug with the <link
xlink:title="OpenStack Wiki"
xlink:href="http://bugs.launchpad.net/openstack-manuals/+filebug"
>documentation</link> (http://bugs.launchpad.net/openstack-manuals/+filebug)</para>
</listitem>
<listitem>
<para>Report a bug with the <link
xlink:title="OpenStack Wiki"
xlink:href="http://bugs.launchpad.net/openstack-api-site/+filebug"
>API
documentation</link> (http://bugs.launchpad.net/openstack-api-site/+filebug)</para>
@@ -408,7 +363,7 @@
<title>Join the OpenStack Community</title>
<para>Since you've made it this far in the book, you should
consider becoming an official individual member of the
community and <link xlink:title="OpenStack Wiki"
community and <link
xlink:href="https://www.openstack.org/join/">Join The
OpenStack Foundation</link>
(https://www.openstack.org/join/). The OpenStack
@@ -460,25 +415,25 @@
ideas and propose a session to the design summit. If the
design summit has already passed, you may also create a
blueprint directly. Read this <link
xlink:title="OpenStack Wiki"
xlink:href="http://vmartinezdelacruz.com/how-to-work-with-blueprints-without-losing-your-mind/"
>blog post about how to work with
blueprints</link> (http://vmartinezdelacruz.com/how-to-work-with-blueprints-without-losing-your-mind/)
for a developer intern's perspective, Victoria
Martínez.</para>
<para>The roadmap for the next release as it is developed can
be seen at <link xlink:title="OpenStack Wiki"
be seen at <link
xlink:href="http://status.openstack.org/release/"
>Releases</link>
(http://status.openstack.org/release/).</para>
<para>To determine the potential features going in to future
releases, or to look at features implemented previously,
take a look at the existing blueprints such as <link
xlink:title="OpenStack Wiki"
xlink:href="https://blueprints.launchpad.net/nova"
>OpenStack Compute (nova) Blueprints</link>
(https://blueprints.launchpad.net/nova), <link
xlink:title="OpenStack Wiki"
xlink:href="https://blueprints.launchpad.net/keystone"
>OpenStack Identity (keystone) Blueprints</link>
(https://blueprints.launchpad.net/keystone) and release
@@ -500,7 +455,7 @@
<tr>
<td><para>Grizzly</para></td>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/GrizzlyReleaseSchedule"
>Under development, Release
schedule</link>
@@ -513,7 +468,7 @@
<td rowspan="4"><para>Current stable release,
security-supported</para></td>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/Folsom"
>2012.2</link>
</para></td>
@@ -523,7 +478,7 @@
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/2012.2.1"
>2012.2.1</link>
</para></td>
@@ -532,7 +487,7 @@
<tr>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/2012.2.2"
>2012.2.2</link>
</para></td>
@@ -541,7 +496,7 @@
<tr>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/2012.2.3"
>2012.2.3</link>
</para></td>
@@ -552,7 +507,7 @@
<td rowspan="4"><para>Community-supported,
security-supported</para></td>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/Essex"
>2012.1</link>
</para></td>
@@ -561,7 +516,7 @@
<tr>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/2012.1.1"
>2012.1.1</link>
</para></td>
@@ -570,7 +525,7 @@
<tr>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/2012.1.2"
>2012.1.2</link>
</para></td>
@@ -579,7 +534,7 @@
<tr>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/2012.1.3"
>2012.1.3</link>
</para></td>
@@ -590,7 +545,7 @@
<td rowspan="2"
><para>Community-supported</para></td>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/Diablo"
>2011.3</link>
</para></td>
@@ -599,7 +554,7 @@
<tr>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/2011.3.1"
>2011.3.1</link>
</para></td>
@@ -609,7 +564,7 @@
<td><para>Cactus</para></td>
<td><para>Deprecated</para></td>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/Cactus"
>2011.2</link>
</para></td>
@@ -619,7 +574,7 @@
<td><para>Bexar</para></td>
<td><para>Deprecated</para></td>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/Bexar"
>2011.1</link>
</para></td>
@@ -629,7 +584,7 @@
<td><para>Austin</para></td>
<td><para>Deprecated</para></td>
<td><para>
<link xlink:title="OpenStack Wiki"
<link
xlink:href="https://wiki.openstack.org/wiki/ReleaseNotes/Austin"
>2010.1</link>
</para></td>
@@ -648,29 +603,29 @@
principles of iterative work, with bug logging,
investigating, and fixing.</para>
<para>Just like the code, the <link
xlink:title="OpenStack Wiki"
xlink:href="http://docs.openstack.org"
>docs.openstack.org</link> site is updated constantly
using the Gerrit review system, with source stored in
GitHub in the <link xlink:title="OpenStack Wiki"
GitHub in the <link
xlink:href="http://github.com/openstack/openstack-manuals/"
>openstack-manuals</link> (http://github.com/openstack/openstack-manuals/)
repository and the <link xlink:title="OpenStack Wiki"
repository and the <link
xlink:href="http://github.com/openstack/api-site/"
>api-site</link> (http://github.com/openstack/api-site/)
repository, in DocBook format.</para>
<para>To review the documentation before it's published, go to
the OpenStack Gerrit server at <link
xlink:title="OpenStack Wiki"
xlink:href="http://review.openstack.org"
>review.openstack.org</link> and search for <link
xlink:title="OpenStack Wiki"
xlink:href="https://review.openstack.org/#/q/status:open+project:openstack/openstack-manuals,n,z"
>project:openstack/openstack-manuals</link> or <link
xlink:title="OpenStack Wiki"
xlink:href="https://review.openstack.org/#/q/status:open+project:openstack/api-site,n,z"
>project:openstack/api-site</link>.</para>
<para>See the <link xlink:title="OpenStack Wiki"
<para>See the <link
xlink:href="https://wiki.openstack.org/wiki/How_To_Contribute"
>How To
Contribute</link> (https://wiki.openstack.org/wiki/How_To_Contribute)
@@ -728,19 +683,19 @@
<para>If the issue is extremely sensitive, send
an encrypted email to one of the Team's
members. Find their GPG keys at <link
xlink:title="OpenStack Wiki"
xlink:href="http://www.openstack.org/projects/openstack-security/"
>OpenStack Security</link>
(http://www.openstack.org/projects/openstack-security/).</para>
</listitem>
</itemizedlist>
<para>You can find the full list of security-oriented teams
you can join at <link xlink:title="OpenStack Wiki"
you can join at <link
xlink:href="https://wiki.openstack.org/wiki/SecurityTeams"
>Security
Teams</link> (http://wiki.openstack.org/SecurityTeams).
The Vulnerability Management process is fully documented
at <link xlink:title="OpenStack Wiki"
at <link
xlink:href="https://wiki.openstack.org/wiki/VulnerabilityManagement"
>Vulnerability
Management</link> (https://wiki.openstack.org/wiki/VulnerabilityManagement).</para>
@@ -749,17 +704,17 @@
<title>Finding Additional Information</title>
<para>In addition to this book, there are many other sources
of information about OpenStack. The <link
xlink:title="OpenStack Wiki"
xlink:href="http://www.openstack.org">OpenStack
website</link> (http://www.openstack.org) is a good
starting point, with <link xlink:title="OpenStack Wiki"
starting point, with <link
xlink:href="http://docs.openstack.org">OpenStack
Docs</link> (http://docs.openstack.org) and <link
xlink:title="OpenStack Wiki"
xlink:href="http://api.openstack.org">OpenStack API
Docs</link> (http://api.openstack.org) providing
technical documentation about OpenStack. The <link
xlink:title="OpenStack Wiki"
xlink:href="https://wiki.openstack.org">OpenStack
wiki</link> contains a lot of general information that
cuts across the OpenStack projects including a list of
@@ -768,7 +723,7 @@
>recommended tools</link>
(https://wiki.openstack.org/wiki/OperationsTools ).
Finally, there are a number of blogs aggregated at <link
xlink:title="OpenStack Wiki"
xlink:href="http://planet.openstack.org">Planet
OpenStack</link> (http://planet.openstack.org).</para>
</section>