Benoit Demarets

The Oracle Virtualization team is proud to unveil Oracle VirtualBox 7.2, bringing a new wave of features and enhancements to this widely used, cross-platform virtualization solution. With expanded support for Windows on Arm, improved graphics integration, updated networking, and a refined user interface, VirtualBox 7.2 offers users a more powerful and intuitive virtualization experience. Read on to discover the key highlights and innovations included in this latest release. #virtualbox #release #arm #applesilicon #windows #microsoft https://lnkd.in/d5hCjsA7

92

3 commentaires

And now... More "manage from the cloud" goodness! :) Two weeks ago, we introduced the ability to convert on-premises groups to be cloud managed and now, in collaboration with our colleagues in Exchange we are releasing the ability to manage the *e-mail* properties of a hybrid user that originates from on-premises, in the cloud. This means you no longer have to manage email attributes like proxyAddresses using on premises tools and commands and wait for them to sync. The majority of enterprise customers use Exchange Online for collaboration, yet those who have AD always had to keep around a couple on Exchange servers to manage those attributes. This gets us closer to not needing them (there are still other use cases for them). Less on-premises infrastructure to rely on... One step closer to truly managing your enterprise directory fully from the cloud. https://lnkd.in/gi96m3cH

128

7 commentaires

🚀 New Blog Post Alert! We just published a deep dive into connectivity options between Hub-and-Spoke and Azure Virtual WAN—a must-read for anyone planning or executing a network architecture migration. 🔗 The blog outlines four practical interconnection strategies to support phased transitions and hybrid topologies: 1. Traffic hair-pinning using ExpressRoute 2. Virtual tunnels via SD-WAN or IPSec 3. vNet Peering + vHub coexistence 4. Transit vNet for decentralized workloads 💡 Whether you're designing for coexistence or full migration, this guide offers actionable insights to maintain performance, security, and operational continuity. 📘 Read the full article: https://lnkd.in/gtjyru28 🤝This article was a team effort—special thanks to my former NetSec GBB teammates for the many years of great collaboration: Bruce Cosden, Adam Torkar, Mays Algebary, Shruthi Nair, David Frazee, Adam Stuart, Daniele Gaiulli, Cynthia Treger, Amon Barge, Kevin Lopez, Marc de Droog, Nirmal Thewarathanthri, Kunal Bhatia, Shabbir Ahmed. 🤝Also, thank you to the Tech Strategy team for the valuable insights: Ethan Haslett, Mauricio Rojas, Rodrigo Reis, Jimmy Maysonet Avila, Recep Ozkurt and anyone else whose name I may have missed. #Azure #VirtualWAN #Networking #CloudArchitecture #HubAndSpoke #Migration #AzureNetworking #CloudStrategy #NetSecGBB

238

7 commentaires

🚀 Query AWS CloudTrail events with AI Agents like Q Developer! The AWS Labs Model Context Protocol (MCP) Server for CloudTrail lets your AI agents directly query AWS account activity for security investigations, compliance audits, and operational troubleshooting. It gives agents unified access to CloudTrail events and CloudTrail Lake analytics — making it easy to track API calls, analyze user actions, and uncover advanced security insights. By standardizing access through MCP, it eliminates the need for custom API integrations, helping AI systems gain seamless visibility and smarter audit capabilities across your AWS environment. Tutorial link (6 minutes 54 seconds): https://lnkd.in/gTBSDQks #aws #q #mcp #cloudtrail

163

2 commentaires

End-to-End Observability with OpenTelemetry in OpenShift In today’s cloud-native world, observability is not optional—it’s the backbone of resilience, performance, and trust in digital platforms. For organizations running workloads on Red Hat OpenShift, achieving true end-to-end observability goes beyond traditional monitoring. We need a unified approach that connects metrics, logs, and traces across applications, containers, service mesh, and platform infrastructure. This is where OpenTelemetry (OTel) becomes the game-changer. As a CNCF project and the emerging industry standard for telemetry, OpenTelemetry offers a vendor-neutral way to collect and correlate observability data. Instead of stitching together siloed tools, we can build a single telemetry pipeline that feeds into multiple backends like Prometheus, Grafana, Jaeger, Tempo, Loki, or commercial APM solutions. So how do we bring this to life in OpenShift? 1️⃣ Application Instrumentation Developers can use OTel SDKs or auto-instrumentation agents (Java, Python, Go, .NET) to capture spans, metrics, and logs directly from code. Context propagation ensures that requests flowing through microservices carry trace identifiers for full request visibility. 2️⃣ OpenTelemetry Collector At the heart of the architecture lies the OTel Collector, deployed natively in OpenShift via the OpenTelemetry Operator. It acts as the universal ingestion layer—receiving data via OTLP, enriching it with attributes (e.g., Kubernetes namespace, pod labels), applying sampling or filtering, and exporting to the chosen backends. Depending on scale, it can run as a sidecar, DaemonSet, or centralized deployment. 3️⃣ Service Mesh Integration For teams leveraging OpenShift Service Mesh (Istio), the Envoy sidecars automatically emit metrics and traces to the OTel Collector. This gives platform teams out-of-the-box visibility into service-to-service communication, latency, and error rates. 4️⃣ Visualization & Alerting Finally, the data flows into backends: Metrics → Prometheus + Grafana for golden signals (latency, errors, saturation, traffic). Traces → Jaeger or Tempo for distributed transaction analysis. Logs → Loki or Elastic for contextual debugging. Alerts → Alertmanager to proactively notify on anomalies. The result? A single pane of glass where developers, SREs, and business stakeholders can align on application health, performance bottlenecks, and user experience. Best practices: Start with high sampling in dev, optimize in prod. Use labels/namespace isolation for multi-tenancy. Secure telemetry pipelines with mTLS. Integrate into CI/CD pipelines for consistent instrumentation. Scale collectors with OpenShift HPA for resilience. As enterprises accelerate into AI-driven digital ecosystems, observability becomes the nervous system. By adopting OpenTelemetry within OpenShift, organizations gain end-to-end insights across apps, services, and infrastructure—without being locked to any single vendor.

23