forked from openstack/kolla
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync upstream june6 #13
Open
JohnGarbutt
wants to merge
63
commits into
cumulus/rocky
Choose a base branch
from
sync-upstream-june6
base: cumulus/rocky
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change adds a new exporter image, the blackbox exporter from the prometheus project [0] that allows external monitoring of resources. [0] https://github.com/prometheus/blackbox_exporter Change-Id: I05ab750d2598ac02df06ee4528a3de12b216e895 Signed-off-by: Jorge Niedbalski <[email protected]> (cherry picked from commit cc7ab30)
There is no way to use neutron-rootwrap-daemon to improve Neutron rootwrap performance at scale with the current Neutron images. Using neutron-rootwrap on huge environment could have a performance impact on many actions and be the root cause of failure during instance creation. Operators should have the choice: - neutron-rootwrap - neutron-rootwrap-daemon Change-Id: I6c65cf6498364e670cc61419dc3a2c19f6fb412d Closes-Bug: #1808457 (cherry picked from commit 4ed611a)
<NOTE: This Rocky backport does not include 1, since the packaging has changed, and mysql_upgrade is already installed.> There are a couple of issues with the mariadb image currently. 1. it doesn't include mysql_upgrade on CentOS/RHEL. It is necessary to run this after an upgrade of MariaDB. This is fixed by installing mariadb-server-utils. 2. it inherits the standard dumb-init entrypoint from the base image, which includes a --single-child argument. That causes signals to be forwarded only to the process executed by dumb-init, which in the case of kolla-ansible is mysqld_safe, however mysqld_safe ignores SIGTERM. After a timeout, Docker then forcibly kills the container. Executing dumb-init without --single-child ensures the TERM signal is sent to mysqld, allowing it to shutdown gracefully. Change-Id: I1a450736721863b91be1ea3d3c8948990de9fdeb Closes-Bug: #1820325 (cherry picked from commit 3075685)
Adding boto3 python library into gnocchi-base image Change-Id: I22119f570172ca93de0587dc3892d8b8de86d525 Closes-bug: #1821580
INFO:kolla.common.utils.kafka:Step 9/12 : RUN curl -sSL -o /tmp/kafka.tgz ${kafka_url} && echo "${kafka_pkg_sha512sum} /tmp/kafka.tgz" | sha512sum -c && tar --strip 1 -xvf /tmp/kafka.tgz -C /opt/kafka && rm -f /tmp/kafka.tgz INFO:kolla.common.utils.kafka: ---> Running in 2b751bf5c975 INFO:kolla.common.utils.kafka:curl (http://apache.osuosl.org/kafka/1.0.2/kafka_2.12-1.0.2.tgz): response: 404, time: 0.198, size: 297 INFO:kolla.common.utils.kafka:/tmp/kafka.tgz: FAILED INFO:kolla.common.utils.kafka:[91msha512sum: WARNING: 1 computed checksum did NOT match Closes-bug: #1822030 Change-Id: Ib9a1bc5c0a69f7780e600404601ae875561450cd (cherry picked from commit 8dfc0ae)
Use the archive URL rather than the current release which has now moved forward. Change-Id: Iab73d3d13025a1498da8c5b573b4cacd8340d3a9 Closes-Bug: #1822956 (cherry picked from 5f83955)
Update bifrost from 5.1.2 to 5.1.3 Update cinder from 13.0.2 to 13.0.3 Update heat-dashboard from 1.4.0 to 1.4.1 Update sahara-dashboard from 9.0.0 to 9.0.1 Update vitrage-dashboard from 1.6.1 to 1.6.2 Update ironic from 11.1.1 to 11.1.2 Update ironic-inspector from 8.0.1 to 8.0.2 Update magnum from 7.0.2 to 7.1.0 Update manila from 7.0.0 to 7.1.0 Update neutron-dynamic-routing from 13.0.0 to 13.0.1 Update neutron-dynamic-routing from 13.0.0 to 13.0.1 Update nova from 18.1.0 to 18.2.0 Update sahara from 9.0.0 to 9.0.1 Update swift from 2.19.0 to 2.19.1 Update vitrage from 3.2.0 to 3.3.0 Change-Id: Ide632797f17b0ac5742fa3f6073f88eb7643d5f4
- Add required packages to run the manila-api service with Apache/mod_wsgi, the mod_ssl package has been added for RHEL/centos/oraclelinux only. - Add necessary cleanup to the start script of the container. - Add directories and configuration files that can be optionally used via Docker entrypoints. Change-Id: Id88760655b3419e7b6bec012ebfda16fb92e5ea3 Implements: bp apache-packages-for-manila-api (cherry picked from commit 170be6d)
When deploying osd, if the user does not use the extra block partition, the kolla will automatically partition the disk and then clean up the data on the disk partition. Sometimes the disk partition will not be updated, there will be an error not finding the partition. This commit fixes the problem. Change-Id: I14708f38614dcb75268c2f460ae3d921748c2d10 Closes-bug: #1824787 (cherry picked from commit ddab09f)
This provides support for building the Monasca fork of Grafana which features Keystone integration. It is primarily for use with the Monasca Grafana datasource, although other datasources can be installed if required. In the future it would be more efficient to build and host the packages externally. Implements: blueprint monasca-grafana Change-Id: I6cb175868d1993ae31700de36b721f4833c4164b
This is split out from Ica9867448dc20864f2fd4614a295a23a4a625af4 which includes an unrelated fix to Percona which is not in Rocky. Co-Authored-By: Martin André <[email protected]> Change-Id: I0f82cc10ebfc2ea60d8e4378e54c63c770e936e7
Ubuntu default-jre-headless is not working with kafka Change-Id: Ic6ab66128efa931277516e0cf5848a816ca676ad Closes-Bug: #1824847 (cherry picked from commit cb8fa69)
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
This includes a bump for bifrost, which is necessary to fix an issue with the conductor failing to start due to an unpinned proliantutils dependency. Change-Id: I40e83c48fb50509c37308faffe069a4dd766a301
backport: rocky, queens A dependency on udevadm was recently added to ironic-lib: https://review.opendev.org/#/q/I9db48a3462422749290bbb887c14816734ab0478 Change-Id: I6c5746606ab59fd88e35525ecc17a62bfa9211e6 Closes-Bug: #1825784 (cherry picked from commit 856b2c8)
Unfortunately Monasca currently requires an old version of InfluxDB. Partially-Implements: blueprint monasca-containers Change-Id: I09af763ef97efc786994c180562861fef96dcc14
Make the filename match with the documentation. TrivialFix Change-Id: Ibcb1149af87f4d999ea7bd9d98782583c7e1a7f3
Monasca-thresh inherits from the Storm container, but we want it to write logs to the Monasca logs directory. In this commit we overwrite the script which configures the Storm log directory with the Monasca script. Change-Id: Id961134e424117ebefb088021faaf37fa02757d7 Partially-Implements: blueprint monasca-containers
The monasca-thresh container is special in that inherits from the Storm container so that it has access to the Storm client. We could make monasca-base inherit from Storm, but it would bloat the other Monasca images which may not run on the same nodes as the Storm topology. Partially-Implements: blueprint monasca-containers Change-Id: Idd1703b72e45bb9d124e06a28738b18da0bc6918
Support has recently been added for managing the Monasca DB with alembic. This change takes advantage of that. Partially-Implements: blueprint monasca-containers Change-Id: I89084ac0076eff099e567b32de249df9f0115e82
Logstash was added to Kolla as part of the effort to deploy Monasca. Monasca uses Kafka messaging version 0.9 which is not supported by Logstash 5.x with the default Kafka input/output plugins. An attempt to downgrade the plugins to the 4.x series which should be compatible with messaging version 0.9 and Logstash 5.x failed. Therefore, until Monasca is upgraded (work is ongoing) this patch downgrades Logstash to 2.4.1. Although it would have been simpler to perform the downgrade by blacklisting the Logstash 5.x package which is provided as part of the official ELK repo and installing the official repo for Logstash 2.4.1, Ubuntu 18.04 no longer accepts SHA1 hashes (for good reason) and will not install Logstash 2.4.1 from this repo (fails with GPG error). This approach does however work for Centos, but for consistency it was not used. This change therefore modifies the Logstash dockerfile, and directly downloads and installs the Logstash 2.4.1 package. It should be reverted as soon as Monasca is upgraded. Partially-Implements: blueprint monasca-containers Change-Id: I58fba9ceded4b3a198136df084c7d37365ab47a8
This is a simple output plugin for Fluentd which can forward logs to the Monasca Log API. Partially-Implements: blueprint monasca-containers Change-Id: I599554052c3cb99ebcbcbc4d7ea1aeb57c573d2e (cherry picked from commit 11611c6)
This includes a bug fix which prevents Fluentd being able to post logs to the Log API. This bugfix is currently only included from Stein onwards. Depends-On: https://review.opendev.org/656294 Change-Id: I1d623a41ca21a93762c4813e9bebca0f55355683
Change-Id: I23869131839ad5c4fa79df39d0409dc1b5d28a35
When 4 or 5 mons are deployed, all mons will always be in the election state, and the ceph cluster cannot be accessed. After comparing with ceph-deploy, I found that when the cluster was initialized, it did not use monmap. When adding a new mon node, it needs to use monmap. According to the above situation, I fixed the problem. Change-Id: Idbfc6741d371adcb06ed97d578d75d3bce862743 Closes-bug: #1824783 (cherry picked from commit 2858143)
Add a trigger for running CI ceph jobs when docker/ceph/.* and docker/cinder/.* files are being changed. Change-Id: I0a5fc2d47ccb4f64dbf8fca7092240cd40777b28 (cherry picked from commit 14f1507)
Bump version to include support for setting log message field name. Change-Id: Ib3953b49247bb36ac8ce25578c05c6bcb2a1905a Partial-Bug: #1830184
The RDO openstack-nova-placement-api RPM ships with an HTTP configuration deploying placement on port 8778, while Kolla-Ansible creates another file to configure it to listen on port 8780. If `placement_api_port` is changed to use port 8778, the placement_api container will fail to start because the port is already in use. This commit removes the configuration file shipped with the RPM package to avoid this conflict. Change-Id: I7babdb794bec3b08047101e2537f030e2217cedb Closes-Bug: #1830420
…api RPM" into stable/rocky
Change-Id: I846989b16fa7f76b11b309b7a9764cec8aaf538d (cherry picked from commit 5e89fbd)
This may break Monasca which can be fixed when it's fully backported to Rocky.
This adds support for building an mtail image for generating metrics from logs. These metrics can then be used to trigger alerts. For example, one may want to track user logins, kernel errors, filesystem corruption etc. Partially-Implements: blueprint mtail
This adds a libvirt exporter image for use with Prometheus. Partially-Implements: blueprint libvirt-exporter Change-Id: Ice2af99a323496d3821762851b663899d15f569a
Change-Id: Id138f12e10102a6dd2cd8d84f2cc47aa29af3972
cASO is an OpenStack accounting exporter. For more detail see: https://github.com/IFCA/caso Change-Id: Ief2c554a64ef6cc971635d7e2a718f63c310fbf6
This change was requested upstream.
This uses the binary release from github.
It is recommended to run cASO as a cron job.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.