Hello everyone, We’re currently using Kolla-Ansible stable/2024.1 to manage our OpenStack deployment, including both core services and the Swift object storage backend. aiming to manage both core OpenStack services and the object storage service through a unified lifecycle management tool. We understand that handling large volumes of data can impact the performance of other services. To mitigate this, we've separated the data path entry points that could become bottlenecks into dedicated and distinct host groups—load balancer and Swift proxy. Specifically, we've introduced two host groups: one for the secondary load balancer (serving as the initial entry gateway) and another for the Swift proxy services. 🔹 **Key Point 1:** We've decoupled the Swift proxy from other OpenStack API services. As a result, the load balancer for Swift must also be isolated from the main load balancer handling other APIs. 🔹 **Key Point 2:** The Swift service registers itself with the existing Keystone service. Depending on the configuration: - If `second_loadbalancer` is enabled, Keystone will expose the load balancer VIP as the endpoint for object storage. - If `second_loadbalancer` is disabled, Keystone will use the direct API address of the Swift proxy. We've attached an architectural diagram to illustrate the overall setup. We’d love to share this approach and welcome any feedback or suggestions from the community. Our broader goal is to eliminate the barriers to managing both storage and OpenStack services simultaneously within a single deployment and through a unified tool. Thanks in advance for your insights!