Operations | Monitoring | ITSM | DevOps | Cloud

For more than a decade we have been concentrating our best talents into two areas. Improving technology and making our products available globally. Now, the time has come to massively scale up our business and technological power.

Kemp, known for its well-tuned and easy-to-use load balancer LoadMaster, has acquired Flowmon, extending its product portfolio and growing through acquisition. So you may ask, how does the technology fit?

By design and tradition, telecoms networks are built to last. But in a world where the rate of innovation seems to be accelerating, the end result is that a lot of legacy infrastructure needs to keep pace with, and accommodate, multiple ‘next generation’ phases. How long this can be maintained before the imperative to rip and replace becomes impossible to ignore is the multi-million-dollar question.

Remote teams are not a new concept. Several organizations have been outsourcing development and support tasks to nearshore and offshore bases for more than a decade. And remote working is gradually increasing given the benefits it gives, like high productivity levels, lower costs, and access to a global talent pool. With the recent COVID-19 outbreak, virtual teams and remote working have truly become mainstream and are being embraced by both employers and employees alike.

If you’re an SRE or on a DevOps team working with Kubernetes and containers, you’ve undoubtedly encountered network connectivity issues with your microservices and workloads. Something is broken and you’re under pressure to fix it, quickly. And so you begin the tedious, manual process of identifying the issue using the observability tools at your disposal…namely metrics and logs.

There are two important protocols required to get your network to forward multicast packets: IGMP and PIM. In this article, I’ll show you how to set up these protocols on your network and how to troubleshoot them. PIM (Protocol Independent Multicast) has two main versions called “dense-mode” and “sparse-mode.” There is also a “sparse-dense-mode,” which has features of both versions and is really just used to help to bootstrap a multicast network.

VMware chose HAProxy as the default load balancer for Tanzu Kubernetes clusters, which helped streamline load balancing in their Kubernetes platform. VMware has delivered vSphere 7 with Tanzu, its endeavor to embed an enterprise-grade version of Kubernetes inside vSphere, the industry-leading compute virtualization platform.