Perspectives, mises à jour et histoires de notre équipe
Navos runs on unmodified upstream Kubernetes and Cluster API. Learn why that architectural choice matters for portability, multi-cloud, and no-lock-in cluster management.
OpenStack controls infrastructure. Kubernetes orchestrates workloads. For AI, you need both. Learn why the combination delivers what neither can alone.
Hardware cycles are accelerating, regulations are multiplying, and costs are rising. A framework for AI infrastructure decisions that last through 2031.
Discover the latest Atmosphere updates with releases 2.3.0, 3.4.0, and 3.4.1, featuring enhanced performance, improved control plane resiliency, and advanced monitoring for load balancers.
We’re excited to announce the latest updates to Atmosphere with the release of versions 2.3.0, 3.4.0, and 3.4.1. These releases bring a range of critical improvements designed to enhance performance, bolster control plane resiliency, and improve monitoring and alerting for load balancer operations.
Version 2.3.0 enhances operational reliability with amphora alerting, improved metrics, and critical bug fixes. Version 3.4.0 introduces Octavia Amphora V2 for resilient load balancer failover, alongside the Valkey service, advanced alerting, and security updates. Version 3.4.1 boosts authentication performance by reactivating the Keystone auth token cache with the latest Ceph update, ensuring faster responses and a more reliable cloud environment.
These updates reflect our continued commitment to building robust, efficient, and resilient infrastructure for modern cloud environments.
Let us dive into the details of each release and what they mean for your operations!
This release focuses on enhancing monitoring, alerting, and overall system stability. Key updates include improved Octavia metric collection via the updated OpenStack database exporter, new alerting capabilities for amphoras in error states, and critical security fixes for the nginx ingress controller. Additionally, bug fixes address instance resizing issues, improve load balancer alert generation, and enhance the stability of the
ERROR state or remains unresponsive for an extended duration.ACTIVE provisioning state while marked as ONLINE. This ensures accurate and timely alerts for transitional states like PENDING_UPDATE. The most important change in this release is the addition of alerting for amphoras to identify cases where an Amphora enters an ERROR state or remains unresponsive for an unexpected duration.
This change significantly enhances the monitoring and operational reliability of load balancers by enabling proactive issue detection and resolution. It ensures that administrators are promptly alerted to potential problems, minimizing downtime and improving the overall stability of services reliant on load balancers.
This release brings significant advancements in load balancing and control plane resiliency with the introduction of Octavia Amphora V2, now enabled by default. Key updates include the addition of the Valkey service, enhanced metric collection and alerting for amphoras, critical security fixes, and multiple bug resolutions to improve overall stability and performance.
ERROR state or remains unresponsive for an extended duration.ACTIVE provisioning states despite being marked as ONLINE. Transitional states like PENDING_UPDATE now properly trigger alerts to ensure accurate monitoring and timely responses. The most important change in this release is the support and default enablement of Octavia Amphora V2. This update enhances control plane resiliency by allowing alternate controllers to resume and complete in-progress load balancer provisioning during control plane host failures. By leveraging persistent task state tracking and monitoring through Jobboard, it effectively resolves the issue of resources being stuck in PENDING states.
This change is critical for ensuring the reliability and stability of load balancer operations. It minimizes downtime, reduces operational disruptions, and provides a more resilient infrastructure that can handle failures without manual intervention. This is essential for environments relying on high availability and seamless load balancing.
This release introduces key enhancements, including performance optimizations, critical bug fixes, improved stability for database clusters, and updated configurations to streamline authentication, storage, and orchestration services.
max_allowed_packet Setting4M to 16M to support larger queries. MySQL 8.x now defaults to 64M, so the configuration no longer explicitly specifies this setting[Cinder]/auth_type Configuration Fixpassword, ensuring full rendering. Alertmanager. timeoutSeconds: 60, failureThreshold: 100) to prevent unnecessary restarts during prolonged operations. The most important change in this release is the reactivation of the Keystone auth token cache, made possible by the resolution of an upstream bug in Ceph (issue 64094) and its inclusion in Ceph version 18.2.7.
This change significantly enhances the performance, scalability, and reliability of Atmosphere's authentication processes. Reactivating the auth token cache reduces the load on the Keystone service by minimizing database queries, leading to faster API responses and more efficient resource utilization. As authentication is a critical component of any cloud environment, this update strengthens the foundation for smoother operations and better user experiences.
As usual, we encourage our users to follow the progress of Atmosphere to leverage the full potential of these updates.
If you require support or are interested in trying Atmosphere, reach out to us! Our team is prepared to assist you in harnessing the power of these new features and ensuring that your cloud infrastructure remains at the forefront of innovation and reliability. Contact us today to explore how these updates can enhance your cloud experience and drive your business forward.
Choose from Atmosphere Cloud, Hosted, or On-Premise.
Simplify your cloud operations with our intuitive dashboard.
Run it yourself, tap our expert support, or opt for full remote operations.
Leverage Terraform, Ansible or APIs directly powered by OpenStack & Kubernetes
