/usr/lib/python2.7/dist-packages/oslo.reports-1.7.0.egg-info/PKG-INFO is in python-oslo.reports 1.7.0-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 | Metadata-Version: 1.1
Name: oslo.reports
Version: 1.7.0
Summary: oslo.reports library
Home-page: http://launchpad.net/oslo
Author: OpenStack
Author-email: openstack-dev@lists.openstack.org
License: UNKNOWN
Description: ===================================
oslo.reports
===================================
.. image:: https://img.shields.io/pypi/v/oslo.reports.svg
:target: https://pypi.python.org/pypi/oslo.reports/
:alt: Latest Version
.. image:: https://img.shields.io/pypi/dm/oslo.reports.svg
:target: https://pypi.python.org/pypi/oslo.reports/
:alt: Downloads
When things go wrong in (production) deployments of OpenStack collecting debug
data is a key first step in the process of triaging & ultimately resolving the
problem. Projects like Nova has extensively used logging capabilities which
produce a vast amount of data. This does not, however, enable an admin to
obtain an accurate view on the current live state of the system. For example,
what threads are running, what config parameters are in effect, and more.
The project oslo.reports hosts a general purpose error report generation
framework, known as the "guru meditation report"
(cf http://en.wikipedia.org/wiki/Guru_Meditation) to address the issues
described above.
Models: These classes define structured data for a variety of interesting
pieces of state. For example, stack traces, threads, config parameters,
package version info, etc. They are capable of being serialized to XML / JSON
or a plain text representation
Generators: These classes are used to populate the model classes with the
current runtime state of the system
Views: views serialize models into say JSON, text or xml. There is also
a predefined view that utilizes Jinja templating system.
There will be a number of standard models / generators available for all
OpenStack services
StackTraceModel: a base class for any model which includes a stack trace
ThreadModel: a class for information about a thread
ExceptionModel: a class for information about a caught exception
ConfigModel: a class for information about configuration file settings
PackageModel: a class for information about vendor/product/version/package information
Each OpenStack project will have the ability to register further generator
classes to provide custom project specific data.
* Free software: Apache license
* Documentation: http://docs.openstack.org/developer/oslo.reports
* Source: http://git.openstack.org/cgit/openstack/oslo.reports
* Bugs: http://bugs.launchpad.net/oslo.reports
Platform: UNKNOWN
Classifier: Environment :: OpenStack
Classifier: Intended Audience :: Information Technology
Classifier: Intended Audience :: System Administrators
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Operating System :: POSIX :: Linux
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
|