| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Currently we are enabling repos irrespective of rpm/deb
statement blocks and not failing in the method used
if a repository is missing.
Downside is - we might be producing one more layer,
but it probably is a more logical approach.
This is required for adding rpm support in repos.yaml
that will also include failing on missing repositories.
Change-Id: I5479c5c935760f00fe4cd307366f261deee3199f
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
|
|
Explicitly set the permissions on the kolla-toolbox kolla_extend_start
file. Also, since all extend_start files are sourced rather than
executed, the executable bits are now cleared throughout the project.
Change-Id: I5c2deb4a2e33575d57c852089f856a9acc6818d0
|
|
We have one install_type only now so that infra stuff is not needed
anymore.
Change-Id: I60d50ba7699d46d001eaef365fb84b0ce8e9b262
|
|
Hacluster-pacemaker images need to have pacemaker cli utils
available in all distros and they are provided by pacemaker-cli-utils
package in Debuntu systems. Due to a different dependency chain
this package is not installed in Debian. This package is also
*recommended* dependency of pacemaker and pacemaker-remote in both
Debian/Ubuntu systems, but unfortunatelly it is not installed
on Debian via APT by default.
This patch adding this package to list of package to be installed
on Debian/Ubuntu systems for both hacluster-pacemaker (required)
and hacluster-pacemaker-remote (to ease with debugging).
Closes-Bug: #1934788
Change-Id: I055086ab4af37878e81844f1055bc48d84ae9945
|
|
Defaults to 'image_prefix' for now but shows which images gets their
names changed soon.
Change-Id: I0608e8f62f28d6667b4c8753c47553e4cbf75503
|
|
CentOS 8.1 came with HA repo. So we can use it.
hacluster-pcs image is disabled as we lack 'crmsh' package for it.
Partially-Implements: blueprint centos-rhel-8
Co-Authored-By: Mark Goddard <mark@stackhpc.com>
Change-Id: I1c786eda399eca4464c9d68ac040c2965350f775
|
|
Change-Id: I9692dda817ef134d647247431565e1b58cf9da41
|
|
Disable external repositories by default and enable only when needed.
Depends-on: https://review.opendev.org/696480
Implements: blueprint repos-off-by-default
Change-Id: Icf2a8397a8349e0fe849d88d160409fd234480a9
|
|
Theses images contains High Availability solution such as
Corosync, Pacemaker, Pacemaker Remote and PCS.
Change-Id: I86fd145d2998f68b08a16082414b86904971549a
Implements: blueprint pacemaker-container
|
