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: I3e2de2c59bc46594293cfd902098b9ae7292869b
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: I80a2fadf8b16b139d07c48a33c52efd33c66935f
Closes-Bug: #1583994
This change modifies the deployment manifests to use the Kibana VIP
address instead of the one allocated for Elasticsearch. It allows then
the deployer to expose the Kibana dashboard on the public network using
network templates if needed.
Change-Id: I8debb43e3e382a7319a70643116572a7e50cb246
DocImpact: document the Kibana VIP address
Implements-blueprint: kibana-grafana-public-ip-access
Depends-On: Icdf9315239a8fde8b0528f555a89adf0374c408f
An Apache virtual host is configured as a reverse proxy to enforce
basic HTTP authentication.
DocImpact Kibana has now credentials
Change-Id: I65f44534581531a9ff923b54a4b08f77df070040
This patch configures HAProxy to terminate SSL connection when the
support for SSL/TLS is enabled in StackLight.
DocImpact Add support for TLS
Change-Id: Icdff278875d7daf928fa036ec1e4905205791546
Implements: blueprint support-secure-communication
In order to fully wrap up the Elasticsearch configuration including
log management, this commit moves all the Elasticsearch related stuff
from the manifest into a new Puppet module lma_logging_analytics::elasticsearch.
Closes-bug: #1572929
Change-Id: I3dd6d027d2b1de3d6ae3baa01a92dbca1d0ff95b
Elasticsearch and Nginx can be deployed on any network thanks to network
templates. This change removes all the hard-coded dependencies on the
management network. All port numbers for Nginx and Elasticsearch are
also moved to Hiera to make it easier to customize if needed.
Related-Bug: #1514365
Closes-Bug: #1577358
Change-Id: If3656be46d93418a2f481e740c59ec9df5ce8523
- Add firewall rules for corosync communication
- Use dedicated cluster.pp manifest to allow the deployment of coexistant
clusters for LMA plugins
- Use primary role property
Implements: blueprint elasticsearch-clustering
Change-Id: Ibf4c1c4e62f214725875869621b40a3ef4c20e53
These parameters are configured with default values if not provided:
* number_of_replicas
* minimum_master_nodes
* recover_after_time
* recover_after_nodes
Change-Id: I3f4c1135c61b209e6e7b6160142c147721306cf9
Configure a VIP and Corosync/Pacemaker cluster. The plugin must override
Hiera data to set explicitly the corosync node list.
Configure Elasticsearch instances with parameters:
* cluster.name
* unicast discovery
Add firewall rule to allow clustering traffic.
Implements: elasticsearch-clustering
Change-Id: I0636e02113bfdacc776beb20c08cc88308486c29
Andreas Jaeger