forked from openstack/kolla
-
Notifications
You must be signed in to change notification settings - Fork 3
Synchronise master with upstream #395
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
Merged
Merged
Conversation
This file contains hidden or 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
Users can override the upper-constraints.txt by setting the source of openstack-base in kolla-build.conf. However, bifrost-base Dockerfile so far doesn't pass overridden upper-constraints file to Bifrost install playbook resulting the playbook not acknowledging it and just use upstream one. This change sets the source of Bifrost upper-constraints to use upper-constraints of openstack-base for consistency among all Kolla images With this, change the environment variable UPPER_CONSTRAINTS_FILE is only affecting kolla-toolbox image. Therefore, moved UPPER_CONSTRATINS_FILE variable example to the ``kolla_toolbox_pip_conf`` block of kolla-toolbox Dockerfile. Additionally, updated 'Python packages build options' section of documentation to represent latest method of changing Python package related options (including this change). Change-Id: I0a9c782ca1177ef84e4323cb1e5bfac0fb3f383c
Change-Id: I0bdef4252d4f2850d2b1a40feac3c373e5c453e7
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
Change-Id: I0c001c77bae17eace8c9ca9d94828d04101752fe
It has long been sort of an abomination of the container world, let's use this deprecation notice as a motivation to work out a kolla-ansible mechanism utilising regular ironic container images to deploy standalone ironic. Change-Id: I6b4e6edc110eebb524396138d24b873cb4ea6726
Change-Id: If0cd6444e5d0c898d199a98204588f8ffa4351b9
Docker does not support running a container in a given network namespace (netns) so we need a client installed in the Neutron container images. Related-Bug: #1891469 Change-Id: I5349449183dbb7f4ec2042a21526076fb42591b3
priteau
approved these changes
Mar 31, 2025
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.
This PR contains a snapshot of master from upstream master.