| Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Iceb16a5cf2ebc64effe30bbc9144144cdffebab0
|
|
When building an image, the RUN command grants
permissions which causes the previous layer
to be copied.
During the test, the image was reduced from 2.84GB to 1.57GB
Closes-Bug: #2104007
Change-Id: I7d2367d4c277287f4db2885f5720a35d934f94b7
|
|
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
|
|
This reverts commit 3c49991a86cb26dd0447fa748d1df9df5aed92bb.
Reason for revert: bug fixed upstream https://github.com/opensearch-project/OpenSearch-Dashboards/pull/8097
Change-Id: Icc810554dc877c9dedaf26609d59a93059a38ba7
|
|
OpenSearch Dashboards 2.16.0 discover page hangs after initial
deployment due to an upstream bug [1].
This change fixes the issue by pinning OpenSearch Dashboards to 2.15.
Note that it seemed safer not to pin OpenSearch to fix this issue, to
avoid breaking deployments that have already deployed 2.16.
[1] https://github.com/opensearch-project/OpenSearch-Dashboards/issues/7626
Closes-Bug: #2077319
Change-Id: I0de9928b2657ab5f31580325e866bff28f2b5510
|
|
This reverts commit 19a004e0a500ea4839fa1e089e1c50c953cec3b3.
Reason for revert: Fixed
Change-Id: I5491adef46fe0cec013a597cb05018d8d7e862f0
|
|
Since 2.13 OpenSearch and OpenSearch-Dashboards packages
install files in /usr/share/opensearch and
/usr/share/opensearch-dashboards with root:root ownership
instead of using opensearch/opensearch-dashboards user.
Closes-Bug: #2061877
Change-Id: I3831d8ab76c8c7136ce7869db3d0d1e05b4ba8f8
|
|
pin opensearch and opensearch-dashboards to 2.12. for now
Closes-Bug: #2060668
Related-Bug: #2060306
Change-Id: I3df4823d78474d94e138ff73f0f577bd247bdad0
Signed-off-by: Sven Kieske <kieske@osism.tech>
|
|
Since 2.12 OpenSearch requires setting initial admin password,
that is not trivial/weak.
Closes-Bug: #2054586
Change-Id: I6b6ef656bc2009a2dc3cdfcb01956d50fba4b7b9
|
|
Change-Id: Id6db7ffb22b3f63e9a406455d52078b76071672f
|
|
Since we moved to using rpm/deb packages, the user has changed.
Related-Bug: #2020152
Change-Id: I2a5a0d761223b4e99c8df59f80261108380d5038
|
|
systemd-tmpfiles is needed otherwise opensearch
postinst on Debian/Ubuntu fails
Change-Id: I5aeb5796f8de7697a1c4a7404fe292ef9eb522ee
|
|
Depends-on: https://review.opendev.org/c/openstack/kolla/+/872557/
Change-Id: I2c71a6ecd114d84291e3564e07e7c3c160f53b33
|
|
Change-Id: I886da6215c20a3d0227b4ee5d603a7e416929618
|
|
Handles x86-64 and aarch64 targets.
Change-Id: I70e2bb1d2744d38e08f5a9a79ab6a7265ebf24c9
|