badc30fcf2
Release notes are version independent, so remove version/release values. We've found that projects now require the service package to be installed in order to build release notes, and this is entirely due to the current convention of pulling in the version information. Release notes should not need installation in order to build, so this unnecessary version setting needs to be removed. This is needed for new release notes publishing, see I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting at http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html . Change-Id: I6158691a389bd8a6c16253284673b3d621907080 |
||
---|---|---|
api-ref | ||
config-generator | ||
devstack | ||
doc | ||
etc/monasca | ||
monasca_events_api | ||
playbooks/legacy/monasca-tempest-events-base | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
.zuul.yaml | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
OpenStack Monasca-Events-Api
OpenStack Monasca-Events-Api provides RESTful Api to collect events from OpenStack cloud.
OpenStack Monasca-Events-Api is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
For the more information of OpenStack APIs, SDKs and CLIs, please see:
Developers
For information on how to contribute to Monasca-events-api, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests as well as linters.
Further developer focused documentation is available at:
Operators
To learn how to deploy and configure OpenStack Monasca-events-api, consult the documentation available online at:
Bug tracking
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at: