Archive

Category Archives for "Networking"

Securing Native Cloud Workloads with VMware NSX Cloud Blog Series – Part 1: Getting Started

Introduction

As businesses evaluate their applications in the constantly evolving world of IT, new strategies are emerging for delivery. These strategies include keeping applications on-premises or moving them to one or more public cloud providers.

These public clouds come with their own networking and security constructs and policy management. This results in a new set of technology siloes that increases expense, complexity and risk:

This blog series will discuss the challenges of providing consistent networking and security policies for native cloud workloads, the value of VMware NSX Cloud, and walk through the process of securing and connecting applications running natively in the public cloud.

VMware NSX Cloud

VMware’s strategy is to enable businesses to create and deliver applications. To support new delivery strategies, VMware NSX Cloud provides consistent networking and security for native applications running in multiple public and private clouds. Utilizing a single management console and a common application programming interface, VMware NSX Cloud offers numerous benefits:

  • Unified Micro-Segmentation Security Policies – VMware NSX Cloud provides control over East-West traffic between native workloads running in public clouds. Security policies are defined once and applied to native workloads. These policies are supported in multiple AWS accounts, regions, and VPCs. Policies are Continue reading

Securing Native Cloud Workloads with VMware NSX Cloud Blog Series – Part 1: Getting Started

Introduction As businesses evaluate their applications in the constantly evolving world of IT, new strategies are emerging for delivery. These strategies include keeping applications on-premises or moving them to one or more public cloud providers. These public clouds come with their own networking and security constructs and policy management. This results in a new set of... Read more →

The loss of net neutrality: Say goodbye to a free and open internet

Update May 17, 2018 Following the U.S. Senate’s 52-47 vote to reinstate net neutrality rules, U.S. Rep. Mike Doyle (D-Pa.) announced the House of Representatives will attempt to also force a vote on the issue under the Congressional Review Act (CRA).“I have introduced a companion CRA in the House,” Doyle said during a press conference yesterday, “but I’m also going to begin a discharge petition, which we will have open for signature tomorrow morning. And I urge every member who supports a free and open internet to join me and sign this petition, so we can bring this legislation to the floor.”To force a vote in the House, the petition needs 218 signatures. The Democrats hold only 193 seats there, so they need 25 Republicans to switch sides.To read this article in full, please click here

Terminology Tuesday Presents: Microservices

Microservices is the philosophy of designing software programs by breaking what used to be a singular function or command into multiple components, known as services.  The ultimate goal is to reduce complexity and increase speed (basically the goal of anything nowadays).

 

Think of Thanksgiving.  A traditional approach would have the same person cook the entire meal.  And likely even do all the dishes.  Think of a world instead where you can assign different individuals (and ovens!) for cooking the turkey, gravy, mashed potatoes, stuffing and anything else that may grace your table.

 

 

Microservices delivers on this dream but also takes the principle to the next level.  Not just breaking up the request (multi-course dinner) into multiple services (turkey, salad, not burning the garlic bread) but making them really really minute.

 

“Services” that used to be inherently linear can now happen concurrently.  To go back to our Thanksgiving example, you could have the potatoes peeled at the same time they’re being mashed.  If we were able to avoid running into one another (part of the magic of software over families in kitchens) everything would become very efficient.

 

Want Continue reading

BrandPost: SD-WAN Vision vs. Acquisition

The migration of applications to the cloud is motivating enterprises to rethink how they architect their WANs, and this in turn has created the SD-WAN market category. The recent acquisition of VeloCloud by VMware, and of Viptela by Cisco earlier in the year, represent attempts by two of the bigger players in IT to stake a claim in this fast-growing new market.While it’s convenient to place products into categories, there are many approaches to SD-WAN, each focused on a different use case or customer base. It was not unexpected to see Cisco go for Viptela. Of all the SD-WAN solutions, Viptela is arguably the one that most closely emulates a traditional router, including conventional device-by-device CLI-based configuration, with a limited amount of central orchestration. It certainly represents the least disruptive approach for Cisco, and gives them an angle to extend the life of the old Swiss army knife known as the ISR.To read this article in full, please click here

How to handle the vanishing radio spectrum: Share frequencies

With the billions of Internet of Things (IoT) devices projected to come on-stream over the next few years, questions are arising as to just where the bandwidth and radio channels are going to come from to make it all work.The sensors need to send their likely increasingly voluminous data back to networks wirelessly to be processed.RELATED: 8 tips for building a cost-effective IoT sensor network But there’s a finite amount of radio spectrum available, and much of it is already allocated to incumbent primary users, such as public safety agencies. Other spectrum is dedicated to mobile network operators who have licensed chunks of it. Some is leftover in the millimeter frequencies, which is thus far pretty much untested in the real world — it’s going to be used for 5G in the future.To read this article in full, please click here

How to handle the vanishing radio spectrum: Share frequencies

With the billions of Internet of Things (IoT) devices projected to come on-stream over the next few years, questions are arising as to just where the bandwidth and radio channels are going to come from to make it all work.The sensors need to send their likely increasingly voluminous data back to networks wirelessly to be processed.RELATED: 8 tips for building a cost-effective IoT sensor network But there’s a finite amount of radio spectrum available, and much of it is already allocated to incumbent primary users, such as public safety agencies. Other spectrum is dedicated to mobile network operators who have licensed chunks of it. Some is leftover in the millimeter frequencies, which is thus far pretty much untested in the real world — it’s going to be used for 5G in the future.To read this article in full, please click here

IDG Contributor Network: The future of SD-WAN: Gen2 is here

SD-WAN is the hottest topic in networking today. On the one hand, analyst reports state that this industry is in its infancy with less than 5% adoption through 2017. On the other hand, the same analysts project over 50% customer adoption in the next 36 months. Why has adoption been modest to-date, and why is 10X acceleration expected now? The answer lies in understanding the differences between the first generation of SD-WAN (Gen1) and the second generation of SD-WAN (Gen2).In the old days, WAN routers were focused on providing connectivity using MPLS. The goal of Gen1 SD-WAN was to enable usage of broadband for connectivity. So Gen1 SD-WAN provided better VPN manageability and improved the delivery of voice traffic over broadband connections. However, like many first-generation products, Gen1 SD-WAN has serious limitations, three of which I examine below.To read this article in full, please click here

IDG Contributor Network: The future of SD-WAN: Gen2 is here

SD-WAN is the hottest topic in networking today. On the one hand, analyst reports state that this industry is in its infancy with less than 5% adoption through 2017. On the other hand, the same analysts project over 50% customer adoption in the next 36 months. Why has adoption been modest to-date, and why is 10X acceleration expected now? The answer lies in understanding the differences between the first generation of SD-WAN (Gen1) and the second generation of SD-WAN (Gen2).In the old days, WAN routers were focused on providing connectivity using MPLS. The goal of Gen1 SD-WAN was to enable usage of broadband for connectivity. So Gen1 SD-WAN provided better VPN manageability and improved the delivery of voice traffic over broadband connections. However, like many first-generation products, Gen1 SD-WAN has serious limitations, three of which I examine below.To read this article in full, please click here

Thoughts on Open/R

Since Facebook has released their Open/R routing platform, there has been a lot of chatter around whether or not it will be a commercial success, whether or not every hyperscaler should use the protocol, whether or not this obsoletes everything in routing before this day in history, etc., etc. I will begin with a single point.

If you haven’t found the tradeoffs, you haven’t looked hard enough.

Design is about tradeoffs. Protocol design is no different than any other design. Hence, we should expect that Open/R makes some tradeoffs. I know this might be surprising to some folks, particularly in the crowd that thinks every new routing system is going to be a silver bullet that solved every problem from the past, that the routing singularity has now occurred, etc. I’ve been in the world of routing since the early 1990’s, perhaps a bit before, and there is one thing I know for certain: if you understand the basics, you would understand there is no routing singularity, and there never will be—at least not until someone produces a quantum wave routing protocol.

Ther reality is you always face one of two choices in routing: build a protocol specifically tuned Continue reading

OpenStack and CITC – Creating and learning about OpenStack networking

Part 1 – Examining the existing network

In my previous post, I was playing around with Cumulus in the Cloud (CITC) and how it was integrated with OpenStack. Now that I was playing with OpenStack in CITC, I wanted to dive deeper into the networking specific technology.

In this blog post I will be discussing how I leveraged a flat network to initially create simple instance deployments. Then I’ll dive more deeply into how I created a VXLAN network for my OpenStack instances to create more scalable east-west communication. In the previous post I used the CITC console as my primary interface for configuration. This time I will be using an SSH client and the direct SSH information, as the outputs I’m gathering have wider width that is easier to obtain via an SSH client.

To do so, I just clicked the SSH access button on the right hand side of the GUI. This provided me with the username, password and IP address that would allow me to use my own SSH client to connect to the CITC infrastructure.

For the uninitiated, here is a great intro doc into OpenStack networking. In addition, my colleague Eric Pulvino pointed me Continue reading