This playbook only matters for multinode since AIO can recover from
power outage without additional configuration.
DocImpact
Implements: blueprint mariadb-lights-out
Change-Id: I903c3bcd069af39814bcabcef37684b1f043391f
The rabbitmq-server package is upgraded to 3.5.7 in cloud-archive
so we update centos to match
The xen-utils package now needs an explict version, xen-utils-4.6 is
what is provided by cloud-archive mitaka
Libvirt 1.3 is in the ubuntu cloud-archive. This has a new daemon for
logging that needs further implementation in newton. For now, it has
been disabled within the qemu.conf
Co-Authored-By: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
TrivialFix
Change-Id: I84217824817c484b6800a64cbd7767b127a3098e
Ubuntu is a bit different than centos. We aren't pinning a single ceph
verion because we cannot. We can however pin to a particular repo,
but we were not due to formating. This fixes that formating and pins
to a specific repo.
TrivialFix
Change-Id: I2f6c4cd2f7d51652dc2729c0ab384165151e94e2
Bug #1549753 raises false alarm about haproxy to the operator and
monitoring tools even though haproxy is running fine and there is
no issue.
haproxy uses UDP datagram socket for logging and the default queue
length of 10 datagrams causes false alert messages in haproxy
logs. This patch set fixes this bug by increasing the queue length
to 128.
Test results of the fix in this patch set are at
http://paste.openstack.org/show/490302/.
Change-Id: I64fdd17cd278d51616aa0dfa4e8d2a422c8ee630
Closes-Bug: #1549753
RDO isn't moving for approxximately 1 week new packages into
current-passed-ci. This blocks Sam's keystone bootstrap patch.
To unblock this, we temporarily have provided copr built RPMs
based upon the srpm from RDO and keystone-master tarball.
TrivialFix
Change-Id: Ic0fe30c56e8dd229f2a25157125272324621bad9
Added missing package for qemu-img in centos container
Added pxelinux.0 in ironic-pxe in centos container
TrivialFix
Change-Id: I706284824f915caf974b1247520c3e4025c47f57
This one line halfs the size of oraclelinux images, from over 1GB to
just over 500MB, bringing them inline with centos.
TrivialFix
Change-Id: I9fd89aeeec56207791fc289db9880b43b17536f5
Add cron image and playbook for logrotate.
The "common" Ansible playbook includes configuration files for
logrotate. At this point the operator cannot customize/override the
logrotate configuration.
Closes-Bug: #1553244
Change-Id: Ic9fdda9a273c9ccd90502f0acc7614d2c7157dca
This was an attempt to get storage_interface to work properly but that
work will not be completed and functional this cycle. There are design
topics that need to be discussed about it that were brought to light
by the RAX gate failing for it.
TrivialFix
Change-Id: I65579f9e0e0dcf3fa51c0ea031ff474145457c40
This will make sure ceph has a quorum and the cluster is functional
before attempting to use it. We also make sure udev has time to create
its links by looping a few times. This resolves the races found in the
bootstrap process
TrivialFix
Change-Id: Ia4624916feb5c80b2a067e5a62c176c1a5dea460
This changes the keepalived extend_start.sh script not to recreate
the /dev/log symlink if it already exists.
This change is related to a comment from SamYaple in
https://review.openstack.org/#/c/288432/.
TrivialFix
Change-Id: I9ca2b4d0b36c961ab3e1e18e2011dd10b47c33e3
This could possibly use gold plating in how bootstrapping
operates to use shade rather than the shell in the container.
It is unclear why stack create failed prior to this patch, but
that fact hasn't changed. I think the heat domains are not setup
properly in the configuration files, meaning that the domain ID
must be created outside of Heat and registered in the configuration
file. This is covered in Bug #1553565.
Change-Id: I490d4dd68a101f388c0ecb4acab54d5eaa6e314e
Partially-Implements: blueprint kolla-upgrade
Implements: blueprint upgrade-heat
mariadb 10 uses the packaging convention MariaDB-* to not
conflict with mariadb 5. As such, MariaDB-devel was indicating
a deprecation warning which this patch removes.
TrivialFix
Change-Id: I4b51fcedce3ef9e44c4a6830cd38ca8040a4d3f6
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
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
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
