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
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
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
Change the code that checks for "lagging" metrics to use this timestamp instead of the Metric timestamp since the lagging code deals with emptying the Kafka queue and this timestamp is a much better measure of how backed up the kafka queue is. The metric timestamp is set by the agent and it is much likelier for the time to be off.
Switch to mon-common build 48 which has the new timestamp. The MetricFilteringBolt will work correctly if the API is using an older version of MetricEnvelope without the timestamp, the lagging code just won't be invoked.
Change the tests to work with the new timestamp.
Had to back down to an older version of scala or the Threshold Engine would not start with a java.lang.NoClassDefFoundError: scala/reflect/ClassManifest
Needed to strip out the storm jar from the consolidated jar.
Needed to remove storm.yaml because Storm complains. Moved the registration of the Serializer to ThresholdingEngine.
Added the storm-core jar to the deb so it can be used for the local mode in mini-mon
Added logback.xml to the deb since storm-core.jar also has a logback.xml and that confuses logback. Ensure our logback.xml is used.
Added the storm-core.jar and logback.xml to the start of thresh in the deb
Had to rework how the AlarmEventForwarder was injected into the AlarmThresholdingBolt because the old way didn't work in a Storm cluster because the TopologyModule wasn't loaded on the worker when prepare was called.
Change so that all view slots must have metrics before the SubAlarm transitions to ALARM. Also, change it so SubAlarmStats doesn't transition it to UNDETERMINED on startup until there have been emptyWindowObservationThreshold calls to evaluate(). Previously it only required one for new sub alarms and sub alarms on restart. Want the ThresholdEngine to have same behavior on restart as it would when the Threshold Engine has been running for a long time.