When we install mesos if it(or some deps) doesn't find java it installs
gcj(java5) which generate cacerts, so later in marathon we have
situation that openjdk8 can't access(discover as broken) to it because
of different format. Additionaly this third-party openjdk8 has in
dependencies ca-certificates-java which need java to generate cacerts
file.
Change-Id: Ic4467529a842ffc4bdd99ac1e23abbdee3a82422
Closes-bug: #1552626
kolla-build currently does not provide information
if docker service is not running. Added exception
handling.
Change-Id: I1f167804b8b4d2ad9220281954ff7ea7162a9817
Closes-Bug:#1553912
When configured with a separate external VIP, glance registry
should listen on only the internal VIP.
TrivialFix
Change-Id: Ie186f2ea391b53b9ea0cb230c573c9e09efd44b2
As we will be switching to pinning versions in Kolla this tool will
help remove the 'manual' part of that equation by looking up the
versions we want.
The idea would be to eventually turn this into an autoproposal bot so
we only ever need to approve changes.
More work can be done here like automatically updating the
kolla-build.conf
Co-Authored-By: Martin André <m.andre@redhat.com>
Partially-Implements: blueprint upgrade-kolla
Change-Id: I052159850b2579ca6db79be71672be382be8a3a3
The new image doesn't have an existing old image, so it
ends up not existing. In this condition, we know that
we are dealing with a version change upgrade.
TrivialFix
Change-Id: Ic2f83c2bb6c34731b60b3430ba66a6324439f0a9
When using separate networks for external APIs and internal
APIs, services need to be configured to use the internal APIs.
The default is typically publicURL.
TrivialFix
Change-Id: I24da63220a65e210c37d9f24b6d76a0031d66f3d
The code in docker/base/start.sh that waits for the log socket does
not work because it includes a bad "space" character after "-S".
This patch changes that character to a real "space" character. It
also sets the SKIP_LOG_SETUP envvar for the Heka container.
TrivialFix
Change-Id: I17a3005df5bbd57678350fc77030e44b5ad6acae
Add documentation for the commit I084e5d1cc8f9993d65167878f9983ad58a68e86e.
Explain how 'build.py' picks up automatically env proxy variables.
Change-Id: Ia8513babd4ff72ed52e167b361d6b54393598a78
Closes-Bug: #1538108
This implements reconfigure for Swift service. Fixes swift-rsyncd in
All-in-One deployment
Partially-Implements: blueprint kolla-reconfig
Change-Id: I82bfa3c73b7365bc3a0ea35d3fc102a3525ebd8c
This patch includes changes relative to integrating Heka with
Elasticsearch and Kibana.
The main change is the addition of an Heka ElasticSearchOutput plugin
to make Heka send the logs it collects to Elasticsearch.
Since Logstash is not used the enable_elk deploy variable is renamed
to enable_central_logging.
If enable_central_logging is false then Elasticsearch and Kibana are
not started, and Heka won't attempt to send logs to Elasticsearch.
By default enable_central_logging is set to false. If
enable_central_logging is set to true after deployment then the Heka
container needs to be recreated (for Heka to get the new
configuration).
The Kibana configuration used property names that are deprecated in
Kibana 4.2. This is changed to use non-deprecated property names.
Previously logs read from files and from Syslog had a different Type
in Heka. This is changed to always use "log" for the Type. In this
way just one index instead of two is used in Elasticsearch, making
things easier to the user on the visualization side.
The HAProxy configuration is changed to add entries for Kibana.
Kibana server is now accessible via the internal VIP, and also via
the external VIP if there's one configured.
The HAProxy configuration is changed to add an entry for
Elasticsearch. So Elasticsearch is now accessible via the internal
VIP. Heka uses that channel for communicating with Elasticsearch.
Note that currently the Heka logs include "Plugin
elasticsearch_output" errors when Heka starts. This occurs when Heka
starts processing logs while Elasticsearch is not yet started. These
are transient errors that go away when Elasticsearch is ready. And
with buffering enabled on the ElasticSearchOuput plugin logs will be
buffered and then retransmitted when Elasticsearch is ready.
Change-Id: I6ff7a4f0ad04c4c666e174693a35ff49914280bb
Implements: blueprint central-logging-service
