Groups Hardware Load Balancer Storage 
Scott Lowe
SEPTEMBER 27, 2019
The “TL;DR” for those who are interested is that this solution bypasses the normal iptables layer involved in most Kubernetes implementations to load balance traffic directly to Pods in the cluster. Servers/Hardware. Unfortunately, this appears to be GKE-specific. Nothing this time around. Virtualization.
Scott Lowe
SEPTEMBER 22, 2017
Servers/Hardware. The series starts with part 0 (preparation), and continues with part 1 (mostly about rpm-ostree ), part 2 (container storage), part 3 (rebase, upgrade, and rollback), part 4 (package layering and experimental features), and part 5 (containerized and non-containerized applications). Virtualization.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scott Lowe
NOVEMBER 16, 2015
Russell Bryant has a couple great articles on OVN— how to test OVN’s “EZ Bake” release with DevStack as well as an article on implementing OpenStack security groups using OVN ACLs (which in turn leverage the integration between Open vSwitch and the Linux kernel’s conntrack module). Servers/Hardware. It’s a whirlwind of technologies.
Scott Lowe
DECEMBER 17, 2015
If you’d like to play around with Cumulus Linux but don’t have a compatible hardware switch, Cumulus VX is the answer. Servers/Hardware. William Lam breaks down the real value of load balancing your PSC in this in-depth article. I would respond to that by saying OpenStack Neutron wasn’t built to manage a physical network.
Fountainhead
JUNE 29, 2009
True, both have made huge strides in the hardware world to allow for blade repurposing, I/O, address, and storage naming portability, etc. However, in the software domain, each still relies on multiple individual products to accomplish tasks such as SW provisioning, HA/availability, VM management, load balancing, etc.
The Accidental Successful CIO
AUGUST 3, 2011
This low level software allowed multiple applications to run on the same physical hardware but believe that they had the box all to themselves. Kotsovinos points out that a VM is really a collection of interconnected physical subsystems : server, storage, and network. The arrival of virtualization software changed everything.
Fountainhead
OCTOBER 6, 2009
A specific angle I want to address here is that of infrastructure automation ; that is, the dynamic manipulation of physical resources (virtualized or not) such as I/O, networking, load balancing, and storage connections - Sometimes referred to as "Infrastructure 2.0". a Fabric), and network switches, load balancers, etc.
Expert insights. Personalized for you.
60 
Let's personalize your content