-
Notifications
You must be signed in to change notification settings - Fork 23
Caracal to Master(Epoxy) forward port #1550
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
Conversation
To avoid disruption to development work, disable the shell timeout for inactivity in the CIS hardening configuration for the `ci-aio` and `ci-multinode` environments.
Set runs-on to accept variables for when sharing workflow.
Add OVN SB Relays
Fix SB relay container tag checking
Switch to StackHPC python upper constraints
Fix broken links in docs
Bump Horizon image to include updated cloudkitty dashboard
Document breaking Keystone LDAP TLS change
Reverts "Track all interfaces in Keepalived" so only HA interfaces are tracked. This prevents L3 HA router flapping when detaching floating IP addresses, because non-HA router interfaces did not include "no_track". Closes-Bug: #2097770
Bump neutron images to fix #2097770
Support for SMS & Leafcloud hosted image builds
fix: typo `ansble` -> `ansible`
Fix Launchpad link in release note
This commit adds additional tempest tests for the following services: - barbican - cinder - cloudkitty - designate - glance - ironic - keystone - magnum - manila - neutron - octavia It also upgrades `kayobe-automation` in order to use the latest `docker-rally` image.
4cdaf6b
to
2f9a00e
Compare
@seunghun1ee the containers on master were built before we had OVN SB relay, so the tag check is now failing because it doesn't exist. Should be easily fixed if you build new OVN containers and update the tag |
03342b7
to
f5c17a3
Compare
All change requests are addressed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK to me, but wasn't sure on the policy of merging branches forwards rather than cherry-picking, so will leave it to someone else to approve.
I think (at least for now) we need to forward porting Caracal to master regularly because it's stackhpc/caracal that people targets when developing a new feature. If stackhpc/master misses these, stackhpc/epoxy in the future will miss new features from Caracal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for being late to the party. I agree with merging instead of cherry-picking while the development is against stackhpc/2024.1
.
No description provided.