Wiredgorilla

Kubernetes provides many critical attributes that can contribute to a robust robotics platform: isolated workloads, automated deployments, self-configuring work processes, and an infrastructure that is both declarative and immutable. However, robots designed with ROS 2 face challenges in setting up individual components on Kubernetes so that all parts smoothly work together. In this blog series, we construct a prototype ROS 2 system distributed across multiple computers using Kubernetes. Our goal is not only to provide you with a working configuration, but also to help you understand why it succeeds and overcome future design challenges. Getting into Kubernetes can be a pretty steep learning curve, so our prototype will use MicroK8s to make it easy. MicroK8s is a lightweight pure-upstream Kubernetes distribution and offers low-touch, self-healing, highly-available clusters. Its low resource footprint makes it ideal for running on robot computers. Even with very little Kubernet

According to leading independent researchers teknowlogy | PAC, open source platforms – and Kubernetes in particular – are central to the future of digital factories.  The PAC RADAR report offers a detailed market analysis of industrial digitalisation trends, and it predicts that Kubernetes-based platforms that bring together edge and cloud technologies will soon dominate the digital factory landscape. This blog will take a closer look at the report’s findings, and examine why Canonical was rated Excellent for industrial edge cloud through the strength of Charmed Kubernetes, MicroK8s and Ubuntu Core. “Kubernetes will be the next big thing at the edge” In recent years, various platforms have emerged to support agile digital factory DevOps, but most industrial edge platforms have been held back by limitations to application scaling and management – and this is where Kubernetes at the edge comes in. Kubernetes is a container orchestration system. Containers make it possible to

Canonical is proud to announce the availability of OpenStack Charms 20.10. This new release introduces a range of exciting features and several improvements which enhance Charmed OpenStack. OpenStack Victoria OpenStack Charms 20.10 brings OpenStack Victoria on Ubuntu 20.04 LTS (via Cloud Archive) and Ubuntu 20.10 with full support from Canonical until April 2022. Victoria is the 22nd release of OpenStack which comes with many interesting features of its own, including solutions for complex networking scenarios. Neutron now provides its metadata service over IPv6 networks which means that users can access it without a configuration drive in IPv6-only networks. Neutron has also added support for flat networks for Distributed Virtual Routers (DVR), Floating IP port forwarding for the OVN backend, and router availability zones in OVN. Octavia load balancer pools now support version two of the PROXY protocol. This allows one to pass client information to member servers when using TCP p

Kubeflow, the ML toolkit on K8s, now fits on your desktop and edge devices! ? Data science workflows on Kubernetes Kubeflow provides the cloud-native interface between Kubernetes and data science tools: libraries, frameworks, pipelines, and notebooks. > Read more about what is Kubeflow Cloud-native MLOps toolkit gets heavy To make Kubeflow the standard cloud-native tool for MLOps within the AI landscape, the open-source community has accomplished the aggregation and integration of many projects on top of Kubernetes. Unfortunately, this notable accomplishment also has a downside. Deploying Kubeflow on your laptop or edge device has become impractical. The very minimum memory necessary to deploy the full Kubeflow bundle is 12Gb of RAM. On top of that, it is Linux-based. This means that on Windows and macOS you need to allocate 12+ Gb of memory to a Linux VM. Last time I tried, my 16Gb of RAM MacBook Pro did not like the idea. Kubeflow lite to experiment on

Another Open Infrastructure Summit just passed, and yet this one was like no other OIS past. Head-sponsoring the first ever virtual OIS was an interesting experience to say the least, with more than 10,000 community members worldwide hoping on the hand-built OIS platform to see what’s new in the open infrastructure space, connect, and – why not? – get their hands on some goodies from their favourite brands! The theme of Open Infrastructure Summit 2020? Couldn’t be more pertinent: ‘The Next Decade of Open Infrastructure’. In other words, this conference was all about change, and evolving to meet with the tech demands to move forward. Canonical had much to say on the topic, with founder and CEO Mark Shuttleworth delivering a live keynote on what he predicts for the future of open infra, as well as a number of our team members giving technical talks on OpenStack related topics such as VNF, OVN, cloud and edge solutions, as well as pricing considerations. You can now access all

In October, we shared a blog post detailing significant snap startup time improvements due to the use of a new compression algorithm. In that article, we focused on the cold and hot application startups, but we did not delve much into the first-run setup scenario. While running our tests, we observed a rather interesting phenomenon, primarily on the Fedora 32 Workstation system. On a particular laptop, we noticed that the initial snap launch took about 60 seconds, whereas cold launches would take about 10 seconds. We decided to analyze this problem, and once we did, we realized there’s an amazing investigative story to be shared, including some really cool findings and general advice for developers on how to optimize their snaps. First-run startup time It is important to note that the difference (6x) was what drew our eye – rather the actual numbers, as these are highly dependent on the platform capabilities and software in question. For that matter, 6-second and 1-second launch ti