Operations | Monitoring | ITSM | DevOps | Cloud

We’ve all heard about cloud-native applications in recent years, but what about cloud-native infrastructure? Is there any reason why the infrastructure couldn’t be cloud-native, too? Or maybe it’s already cloud-native, but you’ve never had a chance to dive deep into the stack to check it out? What does the term “cloud-native infrastructure” actually even mean? The more you think about it, the more confusing it gets.

In the ever-evolving landscape of cloud computing, the concept of a sovereign cloud has recently emerged in response to data management challenges. As governments increasingly recognise the importance of safeguarding their data, ensuring compliance with local regulations, and asserting digital autonomy, sovereign cloud solutions have gained prominence. This blog will explore this concept in detail.

The term High Performance Computing, HPC, evokes a lot of powerful emotions whenever mentioned. Even people who do not necessarily have vocational knowledge of hardware and software will have an inkling of understanding of what it’s all about; HPC solves problems at speed and scale that cannot be achieved with standard, traditional compute resources. But the speed and the scale introduce a range of problems of their own.

As we’ve seen throughout this series, a design pattern is a general solution that has been proven to solve a repeatedly occurring problem when designing software. In my previous blog posts, we examined the basics of the software operator design pattern, the forces impacting it, and the advantages and disadvantages of using it. But how does the software operator pattern actually work?

2023 was an epic year for artificial intelligence. In a year when industry raced faster than academia in machine learning (source), the state of the art for AI evolved to include increasingly larger amounts of data, and bringing to bear sufficient computing resources to support new use cases remained a challenge for many organisations. With the rise of AI, concerns were not far behind.

Whenever it comes to a small-scale private cloud infrastructure project roll-out, organisations usually face a serious dilemma. The implementation process often seems complex due to a lack of knowledge, tricky migrations and an immediate need from management to run various extensions, such as Kubernetes, on top.

As the adoption of confidential computing continues to grow, customers expect their confidential workloads to be strongly separated from their underlying cloud providers. To better align with these user requirements, Canonical is excited to announce ephemeral OS disks for Ubuntu confidential VMs (CVMs) on Microsoft Azure – a new solution that enables you to store disks on your VM’s OS cache disk or temp/resource disk, without needing to save to any remote Azure Storage.

A new upstream Kubernetes release, 1.29, is generally available, with significant new features and bugfixes. Canonical closely follows upstream development, harmonising our releases to deliver timely and up-to-date enhancements backed by our commitment to security and support – which means that MicroK8s 1.29 is now generally available as well and Charmed Kubernetes 1.29 will join shortly.

Ubuntu’s long standing reputation for performance is rooted in our commitment to delivering the latest code, kernels and compilers. This commitment ensures that developers have access to the fastest and most secure environment for their applications. Today Canonical is raising the bar for performance and observability in all of our products.

Canonical announced today that it has joined the board of the OpenAirInterface Software Alliance (OSA) as a Strategic Member. By working together, both organisations aim to develop an end-to-end, open source and open API wireless software stack, and to deliver turnkey solutions for customers and partners.