| Age | Commit message (Collapse) | Author | Files | Lines |
|
[tool.setuptools.data-files] does not support recursive directory
installation. The old setup.cfg [files] worked because PBR's
FilesConfig.expand_globs() used os.walk() to expand docker/*, but
this hook is not triggered by the pbr.build PEP-517 backend.
Move docker/ into kolla/ and use [tool.setuptools.package-data]
instead. Update kolla_worker._get_images_dir() to check the kolla
package directory first so both editable and regular installs work.
Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
The build-date label was rendered into a LABEL instruction on line
3 of every Dockerfile template, immediately after FROM.
Because Docker invalidates the cache for a changed instruction and
all subsequent layers, a date change caused a full rebuild of every
image on each new calendar day, even when nothing else had changed.
Fix this by removing build-date from the Dockerfile templates and
applying it as a --label argument at build time via image.labels.
Labels passed on the build command line are not part of the
Dockerfile cache key, so the date is still recorded in the image
metadata without affecting layer caching.
Change-Id: I8ef0d85bab1a999a4d09f7cbf0c088ca00fdcf77
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
This patch adds a way to patch files in a Docker
image built by Kolla. This is very useful for several
reasons, specifically:
- Custom modifications
- The stable branch of some library has a fix but no pip
package has been released
- Eliminates the need to package your own pip packages
- Eliminates the need to invent your own versioning to prevent
upstream versioning
- Eliminates the need to manage a pip server
- In other words, it eliminates the need to get a wheel into
the image and install it manually using any method not
previously mentioned
It is also highly desirable because, although Kolla can replace
the source for a service with a custom URL for a tarball or its
own Git repo, it cannot do this for dependencies pulled from pip.
I would also like to point out that this is a feature with its own
code path and works only if the user "inserts" a patch into the folder
patches/docker-image/something.patch and creates an analogous series
file for patch source code.
Simply said, this code will never interfere with the upstream build process
since this feature is not intended for use in upstream.
It is rather meant for downstream users who know what they are doing.
Now they just have an option to patch their images.
Everything works on all layers of the Docker image and stores a report
of applied patches which can then be seen in /etc.
This mechanism is similar as debian patch quilt.
Change-Id: I61d0790c5d4d070b7ea9e8c99c0a76ff5d22bf9d
|
|
The cAdvisor update change [1] mistakenly added a reno to the wrong
folder. Moving it back to the correct folder would accidentally add it
to the master branch. Therefore, the reno is being removed.
[1] https://review.opendev.org/c/openstack/kolla/+/704018
Change-Id: I876f3c88c5bcd3c0a7c776796e9870c8512f90e2
|
|
Move most curl sources to sources.py, so it can be automatically
updated in future.
This also makes overriding the versions/locations/sha256 easier.
Change-Id: Ib3497fe96162ae190e5c113cacaaa3ef8334f590
|
|
blackbox_exporter 0.22.0 -> 0.24.0
elasticsearch_exporter 1.5.0 -> 1.6.0
haproxy_exporter 0.13.0 -> 0.15.0
memcached_exporter 0.10.0 -> 0.13.0
mysqld_exporter 0.14.0 -> 0.15.0
node_exporter 1.4.0 -> 1.7.0
ovn_exporter 1.0.6 -> 1.0.7
prometheus 2.38.0 -> 2.48.0
prometheus_alertmanager 0.24.0 -> 0.26.0
prometheus_cadvisor 0.45.0 -> 0.47.2
prometheus_mtail v3.0.0-rc50 -> v3.0.0-rc52
prometheus_msteams 1.5.1 -> 1.5.2
Change-Id: If3f6ff059bedba5c92d97442d77e44aeecef71c4
|
|
blackbox_exporter -> 0.22.0
prometheus_cadvisor -> 0.45.0
elasticsearch_exporter -> 1.5.0
haproxy_exporter -> 0.13.0
prometheus_libvirt_exporter -> 2.3.2
memcached_exporter_version -> 0.10.0
prometheus_msteams -> 1.5.1
prometheus_mtail -> v3.0.0-rc50
mysqld_exporter -> 0.14.0
node_exporter -> 1.3.1
prometheus -> 2.38.0
Change-Id: I3452e8904992bfb977dcae4084a0d98aab82e221
|
|
We have one install_type only now so that infra stuff is not needed
anymore.
Change-Id: I60d50ba7699d46d001eaef365fb84b0ce8e9b262
|
|
This change adds and unifies an ability to override hardcoded URLs for
air-gapped environments via the usual blocks mechanism. Also, this
change replaces ENV with ARG instruction for the variables used only
in building images, and uses bash variable expansion where it possible.
This change is a continuation of the I46b77978926fc2b578a68d1aaa944b2198af0685
Change-Id: I1fbad333b1bc95484e6f4c5145d5936a0e2db84f
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
|
|
Change-Id: I987ea163e4c4e331e0e2c136b7f55890dd9d469b
|
|
This reverts commit 61def281d077f88051d1b1a14dfdbfabac036c8c.
Reason for revert: --location was already in curlrc and it was unified in change I46b77978926fc2b578a68d1aaa944b2198af0685
Change-Id: I066d747400ede30037ff324ad55430af7c35dc18
|
|
-L for curl: If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code), this option will make curl redo the request on the new place
It fixes build error for me:
INFO:kolla.common.utils.prometheus-v2-server: ---> Running in 693fd4095c77
INFO:kolla.common.utils.prometheus-v2-server:curl (https://github.com/prometheus/prometheus/releases/download/v2.23.0/prometheus-2.23.0.linux-amd64.tar.gz): response: 302, time: 0.166583, size: 640
INFO:kolla.common.utils.prometheus-v2-server:
INFO:kolla.common.utils.prometheus-v2-server:gzip: stdin: not in gzip format
INFO:kolla.common.utils.prometheus-v2-server:
INFO:kolla.common.utils.prometheus-v2-server:tar: Child returned status 1
INFO:kolla.common.utils.prometheus-v2-server:tar: Error is not recoverable: exiting now
Change-Id: I095ca6f34cc7c7bca485e9ec019cc52aeb8e3ff4
|
|
Currently we use couple of curl options throughout Dockerfiles, this change
adds all common options to curlrc (-sSLf) and removes usage of those in
Dockerfiles.
Change-Id: I46b77978926fc2b578a68d1aaa944b2198af0685
|
|
Defaults to 'image_prefix' for now but shows which images gets their
names changed soon.
Change-Id: I0608e8f62f28d6667b4c8753c47553e4cbf75503
|
|
Change-Id: I9692dda817ef134d647247431565e1b58cf9da41
|
|
Updates cAdvisor to the latest release for x86 arch. See the change
log for more info [1].
[1] https://github.com/google/cadvisor/blob/master/CHANGELOG.md
Change-Id: I0bd4054e3d2aed67fd27453e3cba321764f09dc9
|
|
Change-Id: I846989b16fa7f76b11b309b7a9764cec8aaf538d
|
|
Obtain binaries from encrypted source when we're unable to check for
their signatures. This should provide better security than downloading
the files over HTTP but does not replace signature verification or file
integrity check.
Related-Bug: #1791674
Change-Id: I7d6eed9ab14ceb130ea4f5f03d893ddaaa0a7acd
|
|
Fixed up 5 Dockerfile.j2 files that had the issue
Change-Id: I8a5551050a75d64712c36d53573437a18777a82f
|
|
Use Debian package from unstable on Debian/aarch64. It works in
stretch-backports container fine and saves us from backporting huge pile
of Golang packages.
Change-Id: Ib4dd540446c58ee69bb46b36f5d7968910943e38
|
|
cAdvisor is a performance monitoring tool for containers which can be used
in conjunction with Prometheus.
Change-Id: Ib329fa30e8ab1c969b3b21bcbccf26bd562b9b83
|