SAF and closed-loop automation Matthias Runge Senior Software Engineer 1
SAF AND CLOSED-LOOP AUTOMATION 2
SAF AND CLOSED-LOOP AUTOMATION Architecture for infrastructure metrics & events AMQ 7 Interconnect - Native AMQP 1.0 Message Router Client Server B Client Large Scale Message Networks ● Offers shortest path (least cost) message routing ○ Server C Used without broker ○ High Availability through redundant path topology ○ and re-route (not clustering) Automatic recovery from network partitioning failures ○ Reliable delivery without requiring storage ○ Client QDR Router Functionality ● Server A Apache QPID Dispatch Router QDR ○ Dynamically learn addresses of messaging endpoints ○ Stateless - no message queuing, end-to-end transfer ○ High Throughput, Low Latency Low Operational Costs 3
SAF AND CLOSED-LOOP AUTOMATION DCN (HCI) Architecture in OSP16 OPTIONAL Undercloud AZ0 AZ0 +Container registry Compute nodes Local ephemeral Ceph cluster 0 Controller nodes OPTIONAL OPTIONAL PRIMARY SITE / Control Stack L3 Routed AZ1 AZ2 AZ3 AZ4 AZn HCI nodes HCI Nodes Compute nodes Compute nodes Compute nodes Ceph + Cinder + Glance Ceph + Cinder + Glance Ceph + Cinder + Glance Ceph + CInder + Glance Ceph + Cinder + Glance DCN SITE / Stack DCN SITE / Stack DCN SITE / Stack DCN SITE / Stack DCN SITE / Stack 1 2 3 4 n 4
SAF AND CLOSED-LOOP AUTOMATION Auto-scaling in OpenStack ● define a “stack” including triggers HEAT AODH ● define an alarm ● periodically check alarm state ● fire event Gnocchi ● act computes Ceilo 5
SAF AND CLOSED-LOOP AUTOMATION All shiny? - wait! This is about OpenStack. Are we adding an additional stack for basic cloud functions? 6
SAF AND CLOSED-LOOP AUTOMATION Conclusion Service assurance framework is able to collect a lot metrics in very short intervals. Using Prometheus and Alertmanager for autoscaling OpenStack causes more issues than it solves. 7
CONFIDENTIAL Designator Thank you linkedin.com/company/red-hat youtube.com/user/RedHatVideos facebook.com/redhatinc twitter.com/RedHat 8
Recommend
More recommend
