Skip to content

ansible

When Hardware Offload Goes Silent: The Case of the Orphaned TC Flowers

In large-scale cloud infrastructure, few things sound as compelling on paper as hardware offloading. When you are running Genestack—powering enterprise OpenStack clouds orchestrated on top of Kubernetes with Kube-OVN and Open vSwitch (OVS)—encapsulating Geneve overlay traffic and tracking connection state can consume measurable CPU cycles across a busy fleet. Offloading those flow tables and match-action rules directly into the physical NIC silicon is the holy grail: line-rate throughput, near-zero CPU overhead, and microsecond packet handling.

Until your network cards decide they cannot actually handle it.

Using ansible to create resources on flex cloud

Ansible has a wide range of modules available to create and manage resources like openstack flavors, images, keypairs, networks, routers among others on the flex cloud. These modules are available in the Openstack.Cloud ansible collection. In this post we will discuss creating resources on flex cloud using ansible modules.

Using ansible to manage instances on flex cloud

In this blog post we will discuss how we can use ansible to manage instances running on a flex cloud. It is important to note that while it is possible to create resources on an openstack cloud using ansible itself but the main aim of this blog post is to discuss how we can manage existing instances running within a project with ansible. The examples provided in this blog post are for instances running ubuntu 20.04 LTS as the base OS; these instructions can be adapted to accomodate any other OS as well