diff --git a/doc/src/docbkx/common/support-compute.xml b/doc/src/docbkx/common/support-compute.xml index 2e851a13f7..8a5a276319 100644 --- a/doc/src/docbkx/common/support-compute.xml +++ b/doc/src/docbkx/common/support-compute.xml @@ -14,27 +14,81 @@ 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. -
- Common Errors and Fixes for OpenStack Compute - 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. +
+ Common Errors and Fixes for OpenStack Compute + 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. Credential errors, 401, 403 forbidden errors - 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. - 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. You may also need to check your proxy settings to see if they are causing problems with the novarc creation. - Instance errors - 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: - libvirt.xml - disk - disk-raw - kernel - ramdisk - console.log (Once the instance actually starts you should see a console.log.) - - 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. - Also check nova-compute.log for exceptions. Sometimes they don't show up in the - console output. - Next, check the /var/log/libvirt/qemu/i-ze0bnh1q.log file to see if it exists and has any useful error messages in it. - - Finally, from the instances/i-ze0bnh1q directory, try virsh create libvirt.xml and see if you get an error there. + 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. + 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. + You may also need to check your proxy settings to see if + they are causing problems with the novarc creation. + Instance errors + 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: + + + libvirt.xml + + + disk + + + disk-raw + + + kernel + + + ramdisk + + + console.log (Once the instance actually starts + you should see a console.log.) + + + 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. + Also check nova-compute.log for exceptions. Sometimes + they don't show up in the console output. + Next, check the /var/log/libvirt/qemu/i-ze0bnh1q.log + file to see if it exists and has any useful error messages + in it. + + Finally, from the instances/i-ze0bnh1q directory, try + virsh create libvirt.xml and see if you + get an error there.
Manually reset the state of an instance diff --git a/doc/src/docbkx/common/support.xml b/doc/src/docbkx/common/support.xml index ab53e6ba0d..77e9ff1408 100644 --- a/doc/src/docbkx/common/support.xml +++ b/doc/src/docbkx/common/support.xml @@ -7,47 +7,42 @@ 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.
Community Support Here are some places you can locate others who want to help. - The Launchpad Answers area - 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: - - OpenStack Compute: https://answers.launchpad.net/nova - OpenStack Object Storage: https://answers.launchpad.net/swift - OpenStack Image Delivery and Registration: https://answers.launchpad.net/glance - OpenStack Identity: https://answers.launchpad.net/keystone - OpenStack Dashboard: https://answers.launchpad.net/horizon - OpenStack Network Connectivity: https://answers.launchpad.net/quantum - - - OpenStack mailing list - 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 https://launchpad.net/~openstack and click "Subscribe to mailing list" - or view the archives at https://lists.launchpad.net/openstack/. You may be interested in the other - mailing lists for specific projects or development - these can be found - on the wiki. + + ask.openstack.org + 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 + http://ask.openstack.org, 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. + + OpenStack mailing lists + 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 https://launchpad.net/~openstack and click + "Subscribe to mailing list" or view the archives at + https://lists.launchpad.net/openstack/. + You may be interested in the other mailing lists for + specific projects or development - these can be found + on the wiki. A description of all the + additional mailing lists is available at + http://wiki.openstack.org/MailingLists. The OpenStack Wiki search The OpenStack wiki 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 @@ 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. - Any deployment specific info is helpful as well. eg. - Ubuntu 12.04, multi-node install. + Any deployment specific info is helpful as well, such as Ubuntu + 12.04, multi-node install. - The Launchpad Bugs areas are available here - OpenStack Compute: - + The Launchpad Bugs areas are available here - : OpenStack Compute: - The OpenStack IRC channel - 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. + + The OpenStack IRC channel + 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 https://wiki.openstack.org/wiki/IRC. +
diff --git a/doc/src/docbkx/openstack-ops/src/ch_ops_upstream.xml b/doc/src/docbkx/openstack-ops/src/ch_ops_upstream.xml index a97922c530..aa11aff2b1 100644 --- a/doc/src/docbkx/openstack-ops/src/ch_ops_upstream.xml +++ b/doc/src/docbkx/openstack-ops/src/ch_ops_upstream.xml @@ -29,55 +29,10 @@ the section below or use one of the channels for support below. Your first port of call should be the official OpenStack - documentation, found on http://docs.openstack.org - You can get questions answered on the Launchpad site for - each project: - - - - Nova Q&A (https://answers.launchpad.net/nova) - - - - Swift Q&A (https://answers.launchpad.net/swift) - - - - Glance Q&A (https://answers.launchpad.net/glance) - - - - Keystone Q&A (https://answers.launchpad.net/keystone) - - - - Quantum Q&A (https://answers.launchpad.net/quantum) - - - - Cinder Q&A (https://answers.launchpad.net/cinder) - - - - Horizon Q&A (https://answers.launchpad.net/horizon) - - + documentation, found on http://docs.openstack.org. + You can get questions answered on the ask.openstack.org site. - Mailing Lists (https://wiki.openstack.org/wiki/Mailing_Lists) @@ -87,7 +42,7 @@ - General list: openstack@lists.launchpad.net. @@ -97,7 +52,7 @@ - Operators list: openstack-operators@lists.openstack.org. @@ -108,7 +63,7 @@ - Development list: openstack-dev@lists.openstack.org. @@ -124,7 +79,7 @@ wiki page where you can search through the discussions. - Multiple IRC channels (https://wiki.openstack.org/wiki/IRC) are @@ -141,7 +96,7 @@ essential to learn how to easily submit a bug report. All OpenStack projects use Launchpad for bug tracking. You'll need to create an account on Launchpad before you can submit a bug @@ -155,96 +110,96 @@ Report a bug in Nova (https://bugs.launchpad.net/nova/+filebug) Report a bug in python-novaclient (https://bugs.launchpad.net/python-novaclient/+filebug) Report a bug in Swift (https://bugs.launchpad.net/swift/+filebug) Report a bug in python-swiftclient (https://bugs.launchpad.net/python-swiftclient/+filebug) Report a bug in Glance (https://bugs.launchpad.net/glance/+filebug) Report a bug in python-glanceclient (https://bugs.launchpad.net/python-glanceclient/+filebug) Report a bug in Keystone (https://bugs.launchpad.net/keystone/+filebug) Report a bug in python-keystoneclient (https://bugs.launchpad.net/python-keystoneclient/+filebug) Report a bug in Quantum (https://bugs.launchpad.net/quantum/+filebug) Report a bug in python-quantumclient (https://bugs.launchpad.net/python-quantumclient/+filebug) Report a bug in Cinder (https://bugs.launchpad.net/cinder/+filebug) Report a bug in python-cinderclient (https://bugs.launchpad.net/python-cinderclient/+filebug) Report a bug in Horizon (https://bugs.launchpad.net/horizon/+filebug) Report a bug with the documentation (http://bugs.launchpad.net/openstack-manuals/+filebug) Report a bug with the API documentation (http://bugs.launchpad.net/openstack-api-site/+filebug) @@ -408,7 +363,7 @@ Join the OpenStack Community Since you've made it this far in the book, you should consider becoming an official individual member of the - community and Join The OpenStack Foundation (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 blog post about how to work with blueprints (http://vmartinezdelacruz.com/how-to-work-with-blueprints-without-losing-your-mind/) for a developer intern's perspective, Victoria Martínez. The roadmap for the next release as it is developed can - be seen at Releases (http://status.openstack.org/release/). 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 OpenStack Compute (nova) Blueprints (https://blueprints.launchpad.net/nova), OpenStack Identity (keystone) Blueprints (https://blueprints.launchpad.net/keystone) and release @@ -500,7 +455,7 @@ Grizzly - Under development, Release schedule @@ -513,7 +468,7 @@ Current stable release, security-supported - 2012.2 @@ -523,7 +478,7 @@ - 2012.2.1 @@ -532,7 +487,7 @@ - 2012.2.2 @@ -541,7 +496,7 @@ - 2012.2.3 @@ -552,7 +507,7 @@ Community-supported, security-supported - 2012.1 @@ -561,7 +516,7 @@ - 2012.1.1 @@ -570,7 +525,7 @@ - 2012.1.2 @@ -579,7 +534,7 @@ - 2012.1.3 @@ -590,7 +545,7 @@ Community-supported - 2011.3 @@ -599,7 +554,7 @@ - 2011.3.1 @@ -609,7 +564,7 @@ Cactus Deprecated - 2011.2 @@ -619,7 +574,7 @@ Bexar Deprecated - 2011.1 @@ -629,7 +584,7 @@ Austin Deprecated - 2010.1 @@ -648,29 +603,29 @@ principles of iterative work, with bug logging, investigating, and fixing. Just like the code, the docs.openstack.org site is updated constantly using the Gerrit review system, with source stored in - GitHub in the openstack-manuals (http://github.com/openstack/openstack-manuals/) - repository and the api-site (http://github.com/openstack/api-site/) repository, in DocBook format. To review the documentation before it's published, go to the OpenStack Gerrit server at review.openstack.org and search for project:openstack/openstack-manuals or project:openstack/api-site. - See the See the How To Contribute (https://wiki.openstack.org/wiki/How_To_Contribute) @@ -728,19 +683,19 @@ If the issue is extremely sensitive, send an encrypted email to one of the Team's members. Find their GPG keys at OpenStack Security (http://www.openstack.org/projects/openstack-security/). You can find the full list of security-oriented teams - you can join at Security Teams (http://wiki.openstack.org/SecurityTeams). The Vulnerability Management process is fully documented - at Vulnerability Management (https://wiki.openstack.org/wiki/VulnerabilityManagement). @@ -749,17 +704,17 @@ Finding Additional Information In addition to this book, there are many other sources of information about OpenStack. The OpenStack website (http://www.openstack.org) is a good - starting point, with OpenStack Docs (http://docs.openstack.org) and OpenStack API Docs (http://api.openstack.org) providing technical documentation about OpenStack. The OpenStack wiki contains a lot of general information that cuts across the OpenStack projects including a list of @@ -768,7 +723,7 @@ >recommended tools (https://wiki.openstack.org/wiki/OperationsTools ). Finally, there are a number of blogs aggregated at Planet OpenStack (http://planet.openstack.org).