Difference between revisions of "Operations"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
So you're an operator using [[OpenStack]]. This page is an attempt to collect recommendations for how to have a good experience running [[OpenStack]]. | So you're an operator using [[OpenStack]]. This page is an attempt to collect recommendations for how to have a good experience running [[OpenStack]]. | ||
| + | |||
| + | = Operations Use cases = | ||
| + | Operators have a variety of things they need to do on a day to day basis. Tracking and classifying these will offer important insight for the developers. Check them out here: [[OperationsUseCases]] | ||
= How to report good bugs = | = How to report good bugs = | ||
Revision as of 00:08, 17 October 2012
So you're an operator using OpenStack. This page is an attempt to collect recommendations for how to have a good experience running OpenStack.
Operations Use cases
Operators have a variety of things they need to do on a day to day basis. Tracking and classifying these will offer important insight for the developers. Check them out here: OperationsUseCases
How to report good bugs
It is often hard for developers to help with bugs filed from operations staff unless they include as much information about the problem experienced. You'll also find that your bug will get more attention if you use the right tags so that its visible to the developers.
Specifically:
- please include the version you're running (both OpenStack release, and where you got the packages from if relevant)
- tag the bug with the "ops" tag
- if you think the bug is trivial, for example a log message emitted at the wrong level, please tag it as "low-hanging-fruit" as well
- include any logs which seem relevant
- describe your production environment -- what database you use, approximately how many machines, et cetera
You can see the current "ops" bugs against nova at https://bugs.launchpad.net/nova/+bugs?field.tag=ops .
