The default nodeset was just changed to focal [1], which in the absence
of the python-is-python3 package doesn't provide a python binary.
[1] https://review.opendev.org/c/opendev/base-jobs/+/789098
Change-Id: I954ec191692c394f546219acdb17afc0f5f916ed
By default Storm uses the in-process ZooKeeper when the local mode
is chosen.
The in-process ZooKeeper doesn't handle the trim of ZooKeeper
Transactional logs & snapshots.
There is a constructor which enables the possibility to use an
external ZooKeeper when the local mode is used. [1][2]
[1] https://issues.apache.org/jira/browse/STORM-213
[2] https://github.com/apache/storm/pull/137/files
Change-Id: I4c6e6f1dbacf093f94b566abc7251f4e33eff93f
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
topology.max.spout.pending allows to limit the number of concurrent
entries sent from spout to worker(s). However, this requires the
usage of a unique id when sending messages (emit).
Change-Id: I907a4574b80e7c3347ba6a9f12c7836767dc3dd7
Story: 2005471
Task: 30550
Zuul job names have been changed in 877f3d60. Update Zuul configuration
to reflect these changes, so that tempest tests are run.
Change-Id: I0b706627eafb7c1d4651679c28b61436e34138ba
Depends-On: https://review.openstack.org/550795
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ibcbc62c9004e4a33a4f9ce3046decfd076bf4f8f
Story: #2002586
Task: #24312
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
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ibcb72c0a85dfb823abecb2814f86312a3bcc5962
Exception on failure to send to Kafka was only being logged
at the debug level. Increased to error level as this is a major
failure in the Threshold Engine functionality
Change-Id: I131d6d7a20cd0e907334cf5d0ff6fac342e8f320
The Alarm state is driven by the last measurement with the newest
timestamp. Use the value even if the measurement is older than the
oldest bucket. This ensures the measurement will be used when the
Threshold Engine is started if the measurement
is received while the Threshold Engine is stopped
Never evaluate subAlarm with function Last except on receiving of
a measurement.
Add tests to ensure this works.
The change is dependent on the monasca-common change and the
change to monasca-api to add the state field to sub_alarm.
Change-Id: Ib5123ed035018757a50d9ebeb7335fbca48054f2
Implements: Blueprint last-value
At the moment it we are using the mysql built in function
NOW() which returns in second resolution.
Change-Id: I1192abb5aab3a9110721cc68f5a1d16a38f77c10
Thresh creates an Alarm when a new Measurement matches an
AlarmDefinition. The previous Thresh code just discarded the
Measurement if it arrived before the newly created SubAlarm,
which was likely to occur. This code saves a Measurement that
does not match an existing SubAlarm in the expectation that the
SubAlarm will arrive very soon. It then adds the Measurement
to the SubAlarm. If the measurement would cause the SubAlarm to
transition to the ALARM state, that happens.
This is more important for determinstic alarms because they will get
fewer Measurements and ignoring the first one may prevent an Alarm's
state going to ALARM when it should
Change-Id: I08e9e481ad55862ba602eba5a68eb371b1d35bbc
Using the standard case of count(log_message) > 1, getting no
log_message measurements should be treated as OK. However, the old code
uses the emptyWindowObservationThreshold for both deterministic and
non-deterministic alarms which means that there must be 3 empty windows
before the deterministic alarm transitions to OK.
This change cause the evaluation of the Alarm to treat an empty window
as OK for deterministic alarms. So, count(log_message) > 1, getting no
measurements in a window will transition the alarm back to OK
Change-Id: I19a04bf78f907b23ef583409f2def54771c07d72
It is possible for the currentValues property to change which can cause
java.util.ConcurrentModificationException. Fix by cloning currentValues
before the SubAlarm gets emitted into storm
Change-Id: I555beffafe0208c0d256732517af401938876d3d
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
'deterministic' being part of alarm expressions
allows monasca-thresh to determine if
given alarms can go back to UNDETERMINED
state or not.
'deterministic' means that alarm
won't ever transititon to UNDETERMINED state,
even if there are no measurements received for
long enough. By default, all alarms
are assumed to be 'non-deterministic' which means
that they can transition to 'UNDETERMINED' state
Implements: blueprint alarmonlogs
Depends-On: Ia42f9a1be37c31416bdac341b092fe527f860c16
Change-Id: Ibe0839123a15494ad45b809e68600c0acef3d330