Impact of Azure Subnets on High Availability Designs
Now that you know all about regions and availability zones (AZ) and the ways AWS and Azure implement subnets, let’s get to the crux of the original question Daniel Dib sent me:
As I understand it, subnets in Azure span availability zones. Do you see any drawback to this? You mentioned that it’s difficult to create application swimlanes that way. But does subnet matter if your VMs are in different AZs?
It’s time I explain the concepts of application swimlanes and how they apply to availability zones in public clouds.
Impact of Azure Subnets on High Availability Designs
Now that you know all about regions and availability zones (AZ) and the ways AWS and Azure implement subnets, let’s get to the crux of the original question Daniel Dib sent me:
As I understand it, subnets in Azure span availability zones. Do you see any drawback to this? You mentioned that it’s difficult to create application swimlanes that way. But does subnet matter if your VMs are in different AZs?
It’s time I explain the concepts of application swimlanes and how they apply to availability zones in public clouds.
Facebook Architects Around Silent Data Corruption
Silent but deadly: there is nothing more destructive than data corruptions that cannot be caught by the various error capture tools in hardware and even in software, can be hard to spot before they have infected an entire application. …
Facebook Architects Around Silent Data Corruption was written by Nicole Hemsoth at The Next Platform.
VPC peering with terraform
I wrote up an example of using terraform modules and provider aliases to turn up interconnected cloud resources (vpcs / vpc peering / peering acceptance / routes) across multiple cloud regions.
Rethinking MPI for GPU Accelerated Supercomputers
In the accelerated era of exascale supercomputing, MPI is being pushed to its logical limits. …
Rethinking MPI for GPU Accelerated Supercomputers was written by Nicole Hemsoth at The Next Platform.
Power To The Kubernetes People
Big Blue shelled out an incredible $34 billion to buy open source infrastructure software juggernaut Red Hat, and it is determined not to just tend and grow that business, which brought in around $3.85 billion in sales in 2019 as the deal closed and probably somewhere around $4.6 billion in 2020. …
Power To The Kubernetes People was written by Timothy Prickett Morgan at The Next Platform.
Automating Red Hat Virtualization with Red Hat Ansible Automation Platform
Red Hat Virtualization (RHV) is a complete, and fully supported enterprise virtualization platform that is built upon a foundation of Red Hat Enterprise Linux (RHEL), oVirt virtualization management projects, and Kernel-based Virtual Machine (KVM) technology in order to virtualize resources, processes and applications.
With RHEL as the compute provider, RHV addsan intuitive web interface with a robust API including SDKs for Java, Ruby, Python, JavaScript and Go for management of virtualization instances and resources that comprise a typical datacenter.
Interacting with an API through a full fledged SDK may present a barrier to datacenter automation due to requisite knowledge of a programming language before getting started. This also means that collaboration may be stifled due to a lack of resources proficient in one of the available SDKs. Standardizing on Ansible for automating RHV allows for all teams and individuals to create and maintain automation without knowledge of a programming language.
Red Hat Ansible Automation Platform allows for interacting with datacenter services in a cleanly formatted and human readable markup language that offers an on-ramp to automating the datacenter. By leveraging the newly released Ansible Content Collection for RHV, this gentle on-ramp to automation becomes more powerful by Continue reading
Automating Red Hat Virtualization with Red Hat Ansible Automation Platform
Red Hat Virtualization (RHV) is a complete, and fully supported enterprise virtualization platform that is built upon a foundation of Red Hat Enterprise Linux (RHEL), oVirt virtualization management projects, and Kernel-based Virtual Machine (KVM) technology in order to virtualize resources, processes and applications.
With RHEL as the compute provider, RHV addsan intuitive web interface with a robust API including SDKs for Java, Ruby, Python, JavaScript and Go for management of virtualization instances and resources that comprise a typical datacenter.
Interacting with an API through a full fledged SDK may present a barrier to datacenter automation due to requisite knowledge of a programming language before getting started. This also means that collaboration may be stifled due to a lack of resources proficient in one of the available SDKs. Standardizing on Ansible for automating RHV allows for all teams and individuals to create and maintain automation without knowledge of a programming language.
Red Hat Ansible Automation Platform allows for interacting with datacenter services in a cleanly formatted and human readable markup language that offers an on-ramp to automating the datacenter. By leveraging the newly released Ansible Content Collection for RHV, this gentle on-ramp to automation becomes more powerful by Continue reading
New Year, New Name: Insights Platform Is Now Internet Society Pulse
In order to align better with the Internet Society’s brand strategy, and to further differentiate our platform from other products with similar names, we have decided to rename our measurement platform.
As of 1 March, 2021, Insights will be known as Internet Society Pulse.
The new URL is: https://pulse.internetsociety.org/
A redirect will be implemented so that anyone navigating to the previous URL will be automatically taken to Internet Society Pulse.
And, if you follow us on Twitter, you’ll see that our handle has been changed from @isoc_insights to @isoc_pulse.
The platform’s look and feel will not change.
Looking Ahead
We launched Insights in early December 2020 and are extremely proud of the impact that the platform has had in just three short months. We’re looking forward to ramping up the platform further in 2021 and will be adding three new focus areas throughout the year:
- Internet Resilience
- The Internet Way of Networking
- Keeping Traffic Local
In 2021, we’ll also expand our analysis and reporting offerings, increase our engagement with the Internet measurements community, bring on board more data partners and add new features to the platform.
Stay up to date by signing up to our mailing list and Continue reading
Attend Future:NET 2021 – A Premier Networking Event
What is Future:NET?
Sponsored by VMware, Future:NET 2021 is the premier thought leadership event on networking of the year. Scheduled for March 23 in AMER and March 24 in EMEA and APJ, the event will be simulcast live around the world—showcasing authentic, in-depth discussions led by the who’s-who of networking leaders. Come prepared to hear open, honest, and sometimes lively conversations about the future direction of networking.
How is Future:NET 2021 Different from Previous Years?
Future:NET has always been an invite-only, in-person event held during VMworld U.S. This year, we are taking it to the next level with a virtual format that will be broadcast live to a global audience on a new, interactive online platform. This will preserve the intimate, authentic feel of past events while allowing participants to share valuable insights with change agents around the world.
Why Attend Future:NET?
Future:NET is a different kind of industry event. While other networking conferences have been reduced to vendor showcases, Future:NET disallows product pitches in favor of open debates that foster in-depth conversation among professionals across the industry. This will not be a VMware showcase or a think tank. Future:NET is a vendor-agnostic industry event led by those who have forecasted, created, or disseminated change and who are lured by new technology and its ability to transform the world. Hear from luminaries such as Albert Greenberg from Azure, Bikash Koley from Google Cloud, Nick McKeown of Stanford University, Pere Monclus from VMware, and Vijoy Pandey from Continue reading
Rethinking BGP on the DC Fabric (part 5)
BGP is widely used as an IGP in the underlay of modern DC fabrics. This series argues this is not the best long-term solution to the problem of routing in fabrics because BGP is not ideal for this use case. This post will consider the potential harm we are doing to the larger Internet by pressing BGP into a role it was not originally designed to fulfill—an underlay protocol or an IGP.
My last post described the kinds of configuration required to make BGP work on a DC fabric—it turns out that the configuration of each BGP speaker on the fabric is close to unique. It is possible to automate configuring each speaker—but it would be better if we could get closer to autonomic operation.
To move BGP closer to autonomic operation in a DC fabric, there are several things we can do. First, we can allow a BGP speaker to peer with any other BGP speaker it receives an open message from—this is often called promiscuous mode. While each router in the fabric will still need to be configured with the right autonomous system, at least we won’t need to configure the correct peers on each router (including the Continue reading
Cloudera Pivots To Data Management As Hadoop Fades
It was only two years ago that Cloudera, once one of the top vendors in what had been a white-hot Hadoop market, found itself fighting for survival. …
Cloudera Pivots To Data Management As Hadoop Fades was written by Jeffrey Burt at The Next Platform.
How to Use Your Own Registry
One of the things that makes the Docker Platform so powerful is how easy it is to use images from a central location. Docker Hub is the premier Image Repository with thousands of Official Images ready for use. It’s also just as easy to push your own images to the Docker Hub registry so that everyone can benefit from your Dockerized applications.
But in certain scenarios, you might not want to push your images outside of your firewall. In this case you can set up a local registry using the open source software project Distribution. In this article we’ll take a look at setting up and configuring a local instance of the Distribution project where your teams can share images with docker commands they already know: docker push and docker pull.
Prerequisites
To complete this tutorial, you will need the following:
- Free Docker Account
- You can sign-up for a free Docker account and receive free unlimited public repositories
- Docker running locally
Running the Distribution service
The Distribution project has been packaged as an Official Image on Docker Hub. To run a version locally, execute the following command:
$ docker run -d -p 5000:5000 --name Continue reading
Network Break 322: Juniper Mist-ifes 128 Technology; US Telcos Spend Big For 5G Spectrum
On today's Network Break we discuss a slate of Juniper announcements around new integrations with its Mist platform, plus new switches. HPE acquires a SaaS company for controlling cloud and infrastructure costs, US telcos spend $81 billion on spectrum for 5G, and we dive into the latest round of financial results from SolarWinds, VMware, and Nutanix.Network Break 322: Juniper Mist-ifes 128 Technology; US Telcos Spend Big For 5G Spectrum
On today's Network Break we discuss a slate of Juniper announcements around new integrations with its Mist platform, plus new switches. HPE acquires a SaaS company for controlling cloud and infrastructure costs, US telcos spend $81 billion on spectrum for 5G, and we dive into the latest round of financial results from SolarWinds, VMware, and Nutanix.
The post Network Break 322: Juniper Mist-ifes 128 Technology; US Telcos Spend Big For 5G Spectrum appeared first on Packet Pushers.
DDoS Mitigation with Juniper, sFlow, and BGP Flowspec
This article discusses how to deploy the DDoS Protect application in a Juniper Networks environment. Juniper has a long history of supporting BGP Flowspec on their routing platforms and Juniper has added support for sFlow to their entire product range, see sFlow available on Juniper MX series routers.
First, Junos doesn't provide a way to connect to the non-standard BGP port (1179) that sFlow-RT uses by default. Allowing sFlow-RT to open the standard BGP port (179) requires that the service be given additional Linux capabilities.
docker run --rm --net=host --sysctl net.ipv4.ip_unprivileged_port_start=0 \
sflow/ddos-protect -Dbgp.port=179
The above command launches the prebuilt sflow/ddos-protect Docker image. Alternatively, if sFlow-RT has been installed as a deb / rpm package, then the required permissions can be added to the service.
sudo systemctl edit sflow-rt.serviceType the above command to edit the Continue reading