This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ibde69865f6443a1641db67b70dd0ab1ea72586e0
Nagios will check for external commands as often as possible.
The number of passive checks have been significantly increased and
Nagios can be the bottleneck with 10s interval with large deployments.
Change-Id: Ic7b38203d6641497f5c8d50076903bd7226ed679
The patch removes the crontab at the begining of deployment and increase
the frequency of the cron job responsible to update Nagios.
Change-Id: I095540c36b3f0c0c318ae91702b5671e3122e8c2
The dummy check is configured when LMA collector plugin is not
installed, this dummy check has been added to allow LMA infrastructure
alerting plugin to be tested alone by the CI.
Change-Id: Ifaec285e2913f8a382e26c363acc15da0aee0eb0
Closes-bug: #1638546
When an alarm contains metric(s) with collected_on:'aggregator',
the corresponding Nagios service check is skipped.
Change-Id: I758e7bd412a68314e59ec86a40370661525a5af9
This patch modifies the cron job used to update the nagios configuration
to solve a bug that occurs when several version of the plugin are
available. This happens after an upgrade procedure.
Change-Id: I41831e43707e7ca5e88fd0a329508ad4813d26bb
Closes-Bug: #1622628
With activate_alarming=false, AFDs are not configured in Nagios,
if 'activate_alarming' is not set the AFDs are configured.
if AFDs are configured and 'enable_notification' and is true, the
notification are enabled.
Change-Id: I561fae6e7e62f237bee58771c91c6344332f239d
blueprint: alarming-refactoring
The latest version of puppetlabs_spec_helper (1.2.0) depends on
rubocop-rspec which itself requires at least Ruby 2.2.
Change-Id: Icdb6277be619d5aa8e2a1a4275df56e0ea9d4222
This patch modifies the check of the hostname in the SSL certificate
to support certificate with wildcard.
Change-Id: Ib2da2fd4bcb103ca9bbe1a892afdb4cf01c59b05
Closes-Bug: #1608665
This patch modifies the label of the radio button used for selecting
the LDAP protocol to make it unique across all the StackLight plugins.
Change-Id: I9fff175af82a5e6bab8666fa5f8c8f1b64926b0c
Partial-Bug: #1599778
Without this change, the nodes are configured to use the Fuel node as
their default gateway. Note that the code path is different between MOS
8 and MOS 9 because of this bug fix [1] that hasn't been backported on
MOS 8.
[1] https://bugs.launchpad.net/fuel/+bug/1541309
Change-Id: I13a504c03091119286b993c626db2379eb27aa29
Closes-Bug: #1583994
This ensures that the Nagios Apache service won't start until the VIP
interfaces are up and running. This is required because the Apache OCF
script needs to tweak the ARP parameters of the VIP interfaces.
Change-Id: I4cc7b7db06cda31064b22e0283af478228202b54
Related-Bug: #1594722
Since Apache runs in its own namespace, it has no default gateway and
can't connect to remote services such as LDAP if those aren't in the
same subnet. As long as one of the 2 VIP addresses is located on the
management network, we should configure the management vrouter as the
default gateway in the infrastructure_alerting network namespace.
Note that it solves the issue when network templates are used and none
of the VIP addresses is located on the management network.
Partial-Bug: #1600167
Change-Id: I61dcdddc92aa705839ff10d841bbcfdc36d29caf
This change fixes the declaration of resource colocations for VIP
addresses and Nagios/Apache. The dependent resource must be listed
first in the array (which isn't obvious!).
Change-Id: If6df9dfa31fa07bd2a06f0d07d92f2a9aa0e3c88
Closes-Bug: #1603319
This is useless to run Nagios in a dedicated namespace and this way, Nagios is
able to communicate with external networks (eg. to send SMTP notifications).
Change-Id: Ica543c29412f109db11dc3bd18ae9e8cecdf1817
The Nagios UI uses now port 80 for HTTP or 443 for HTTPS.
The Nagios WSGI application sticks always with HTTP port 80.
Change-Id: I39d22068a6a50d2b1d7ed7eff8b788b1fe204cdc
Nagios re-configuration relied on the existence of the file
/etc/hiera/nodes.yaml but this file is not more present.
The script relies now on both files astute.yaml and deleted_nodes.yaml
for MOS-9 and still relies on nodes.yaml for MOS-8.
Closes-bug: #1596830
Change-Id: I3ab8ac72d098b43c009a4fc8a7dfb72fab9ca5d4