Commit Graph

5 Commits

Author SHA1 Message Date
Witek Bedyk 811acd76c9 Remove project content on master branch
This is step 2b of repository deprecation process as described in [1].
Project deprecation has been anounced here [2].

[1] https://docs.openstack.org/project-team-guide/repository.html#step-2b-remove-project-content
[2] http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016814.html

Depends-On: https://review.opendev.org/751983
Change-Id: I83bb2821d64a4dddd569ff9939aa78d271834f08
2020-09-15 10:12:44 +02:00
Andreas Jaeger cffdf512c3 Cleanup py27 support
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
  know about the requirement
- Remove obsolete sections from setup.cfg:
  * Wheel is not needed for python 3 only repo
  * Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore

Change-Id: I2c251d4be8f87a0772dbb06083639325e69ed98d
2020-04-05 11:36:39 +02:00
OpenStack Proposal Bot 81b239cc21 Updated from global requirements
Change-Id: Iaaee5ebe873b6868e6503cc166a10637d04c33be
2017-03-17 15:59:01 -07:00
Tony Breeds 51001d206a Manual sync with openstack/requirements
In I530bd05641f39d94e5a543dcbb219a38f08a1460 it's been requested that the
requirements bot sync global requirements to monasca-transform.

This will fail as tox is listed in test-requirements.txt.  This change
remove tox from test-requirements as manually runs the bot against this
repo.  meaning that once the change merges requirements syncs will be
automatic and simpler

Change-Id: I1c5e5c288b86bd44c1346a26079bf8bd9b7b9167
Needed-By: I530bd05641f39d94e5a543dcbb219a38f08a1460
2016-11-28 19:44:00 +11:00
Ashwin Agate 8f61dd95a9 monasca-transform initial commit
The monasca-transform is a new component in Monasca that
aggregates and transforms metrics.

monasca-transform is a Spark based data driven aggregation
engine which collects, groups and aggregates existing individual
Monasca metrics according to business requirements and publishes
new transformed (derived) metrics to the Monasca Kafka queue.

Since the new transformed metrics are published as any other
metric in Monasca, alarms can be set and triggered on the
transformed metric, just like any other metric.

Co-Authored-By: Flint Calvin <flint.calvin@hp.com>
Co-Authored-By: David Charles Kennedy <david.c.kennedy@hpe.com>
Co-Authored-By: Ashwin Agate <ashwin.agate@hp.com>

Implements: blueprint monasca-transform

Change-Id: I0e67ac7a4c9a5627ddaf698855df086d55a52d26
2016-05-26 00:10:37 +00:00