mariadb-connector-j is:
- Well maintained.
- Compatible (v2.7.0) with MySql Server 8.0.x
- LGPL Licensed
Change-Id: I44830b47a1de4ae69f635327a2da1802a67d92d2
Story: 2008236
Task: 41079
MySQL Connector is released under GPLv2 license which restricts the
distribution of the consuming project [1]. This change removes MySQL
Connector and leaves Drizzle JDBC which is licensed under BSD.
[1] https://governance.openstack.org/tc/reference/licensing.html
Story: 2001522
Task: 6324
Change-Id: I4c39ebc290475820b5ba3ab54c36198ca9069abe
Depends-On: https://review.openstack.org/541366
Storm classes changed from starting with backtype to org.apache
Since this is a major backwards incompatible change, increment the
jar version
Copy some Stream classes from monasca-common. They were only used for
monasca-thresh anyways and having them in a separate repo made it
harder to make this change. A later review will remove these classes
from monasca-common
Need to have an explicit dependency on commons-codec
Change-Id: I36db83ce7fdea02ae4df267cf0820e49dcdf3001
Following changes made because monasca-common
was modified:
- removed unnecessary dependencies
- updated hikari version
- added javax.el-api
Change-Id: I176008a258411500bf14ba4a26258bdce90476db
Also, pull and build monasca-common directly instead of using
jars from tarballs.openstack.org since zuul often gets backed
up and jars don't get updated fast enough
Change-Id: I22fc5cfc085a583c337fca199d5e49ead93fcbb7
Create a symlink so the target directory is in the place
the upload expects
Shrink the jar to only what is needed
Change-Id: Idb71dae90db4f6e749cc55ffbb106794a89651e1
The AlarmCreationBolt now caches AlarmDefinitions and Alarms for
quicker evaluation of incoming metrics. Incoming metrics end up in one
of these buckets:
1. Fits into an existing Alarm
2. Causes a new Alarm to be created
3. Already exists in an existing Alarm
All of these require the analysis of existing Alarms. I tried writing SQL
to do this analysis but it just wasn't fast enough so instead I added
the caching of the Alarm Definitions and Alarms.
The AlarmCreationBolt now needs to process Alarm deletion message so
that stream from the EventProcessingBolt had to be hooked up to the
AlarmCreationBolt.
The AlarmCreationBolt used to incorrectly handle
Alarm Definition Updated events.
Improved the queries in AlarmDAOImpl to be more efficient by using
fewer queries intsead of multiple queries per Alarm. However the
AlarmDAOImplTest now requires a real mysql instance since the h2
emulator doesn't understand "group_concat". Mark that test as
only run for target integration-test
Turn on tests for target integration-test
Previous code was not reusing Metrics from existing Alarms
all times it should have. Added test for this case
Changed info messages to debug to lessen normal logging.
Added more tests of existing and new functionality
Added some timing code for debug
Removed unused code
Added more debug logging code
Added reference to API doc for Alarm Definitions in README
Change-Id: Ied9841ecde7608b9eb1eb9c110b73b079ede71bc
not change back to the real state
Get Alarm Deletion to work properly. Previously, it would not clean
up the Alarms or Sub Alarms
Get the Alarm Definition Deletion Event to work correctly. Previously
it wasn't handled
Get the Alarm Definition Updated Event to work correctly, at least
for name, description and severity
Finish implementing some TODOs in AlarmCreationBolt and add tests
Fixed some code that could handle Alarm Definition Updates in
the MetricAggregationBolt but the right calls aren't made in
the rest of the code, yet
Removed some unused or duplicated test java files
Turn the tests back on as they now run
Change-Id: Idb6c92d35e2273601411ca9c0f7d7ba45c61ad55
This code creates Alarms correctly but can't delete them or
Alarm Definitions. It also does not handle Alarm Definition
updates.
This code is dependent on the new monasca-common changes that
have not been merged.
MetricFilteringBolt reads AlarmDefinitions on startup.
MetricFilteringBolt sends the message that a new MetricDefinition
was found for an AlarmDefinition.
MetricAggregationBolt gets SubAlarm messages for SubAlarm creation
instead of getting SubAlarms from the database
Created the AlarmCreationBolt which will handle AlarmCreation when
the metrics that fill an alarm are seen. Also, will add Alarmed Metrics
to an existing alarm if they match.
Temporarily renamed sub_alarm table to sub_alarms table to not conflict
with API table.
Using the BeanMapper to directly map an AlarmDefinition caused an issue
with the older version of guava used by storm so had to hack around that.
Temporarily renamed sub_alarm table to sub_alarms table to not conflict
with API table.
Using the BeanMapper to directly map an AlarmDefinition caused an issue
with the older version of guava used by storm so had to hack around that.
Allow more then one AlarmCreationBolt because it routes by
AlarmDefinitionId
Change the routing for MetricFilteringBolts so they always get the same
tenantId + Metric name. Prevents multiple messages from going to the
AlarmCreationBolt
Removed MetricDefinitionDAO and all related classes since they are
not used anymore
Make it so there is only one AlarmCreationBolt because there is
no code protection for ensuring dimensions aren't created twice
for concurrent creates
Tests are turned off for now
Change-Id: I6747d789bbe0f7f723e19060bf19c3fe318c1e3e
The diffs are going to be very hard to read on this change, but
basically the change is from com.hpcloud.mon to monasca.thresh.
Since monasca-common packages haven't changed, yet, they are still
referenced as com.hpcloud.mon, but everything else has changed to
monasca.thresh.
The init script has also been changed to invoke the new package path.
Change-Id: I5aad9302a8f5b11ed1b9874160f0d7a9882c5b2d
Modified build to work with maven 2
Modified so it will download monasca-common jars
from tarballs.openstack.org if the user is jenkins, otherwise the
user is told to build and install monasca-common
Had to move the source code to the new thresh directory so that a
separate module could do the download before dependencies would
be checked by maven
Had to explicitly set the project name in the control file, not sure
why
Change-Id: Ic4d02478b078aad7c1f0eebda2ea2def8d9edf1a
Martin Chacon Piza