For disaster recovery, political, and organizational reasons, enterprises like to have multiple datacenters, and now they are going hybrid with public cloud capacity adding in the mix. Having networks scattered across the globe brings operational challenges, from being able to easily migrate and manage workloads across the multiple sites and increased complexity around networks, security to adopting emerging datacenter technologies like containers.
As the world becomes more cloud-centric, organizations are looking for ways to gain greater visibility and scalability across their environments, automate as many processes as possible and manage all these sites as a single entity.
Cisco Systems …
Cisco Stretches ACI Network Fabrics, Eases Management was written by Jeffrey Burt at The Next Platform.
Today we start releasing a new video series in Docker’s Modernize Traditional Apps (MTA) program, aimed at IT Pros who manage, maintain and deploy Java apps. The video series shows you how to move a Java EE 7 application written to run on Wildfly 3, move it to a Windows Docker container and deploy it to a scalable, highly-available environment in the cloud – without any changes to the app.
These are the first 4 of a 5 part video series in Docker’s Modernize Traditional Apps (MTA) program, aimed at Java IT Pros. The video series shows you how to move a Java EE app on JBoss Wildfly to a Docker container and deploy it to a scalable, highly-available environment in the cloud – without any changes to the app.

Part 1 introduces the series, explaining what is meant by “traditional” apps and the problems they present. Traditional apps are built to run on a server, rather than on a modern application platform. They have common traits, like being complex to manage and difficult to deploy. A portfolio of traditional applications tends to under-utilize its infrastructure, and over-utilize the humans who manage it. Docker Enterprise Edition (EE) fixes that, giving Continue reading
New Wi-Fi Alliance certification aims to improve connection setup in WiFi networks.
New Wi-Fi Alliance certification aims to improve connection setup in WiFi networks.
One of the design scenarios we covered in Leaf-and-Spine Fabric Architectures webinar is a pure layer-3 data center, and in the “how do I do this” part of that section Dinesh Dutt talked about the details you need to know to get this idea implemented on Cumulus Linux.
We covered a half-dozen design scenarios in that webinar; for an even wider picture check out the new Designing and Building Data Center Fabrics online course.
![]() |
| Fig 1.1- VSS using SUP Engines |
Projects are the latest attempts by vendors to ease container management.
SolidFire Element OS is an integral part of NetApp HCI.
Yesterday we published a new policy brief: Spectrum Approaches for Community Networks
Access to affordable and available spectrum is critical for Community Networks. Policy makers can play a key role in ensuring adequate access to spectrum. The policy brief examines the various ways that Community Networks can gain access to spectrum, including:
Network operators also play a key role in helping Community Networks. The policy brief outlines recommendations for operators which include:
Please read our press release for more information about this new paper. Also visit our World Telecommunications Development Conference (WTDC) 2017 page for more about what our team is doing there in Buenos Aires this week.
The post New Policy Brief published on Community Networks and Access to Spectrum appeared first on Internet Society.
Part three! Let’s get straight to business and carry on where we left off from part two.
Thinking about automation in an agnostic way is your first footstep. Automation is about data flowing through building blocks that do things and decision points, allow you when to do things.
Removing CLI and replacing it with an abstraction layer isn’t much of a win. For instance, I regularly talk about the process of creating a VLAN and applying it to an Ethernet switch-port on a tagged interface. This somewhat simple ‘workflow’ creates more conversational friction than imagine-able. Let’s work through it.
Task: Create a VLAN
This task requires domain-specific parameters to a VLAN. These are: ‘VLAN_Number’ and ‘VLAN_Description’.
Task: Apply VLAN to Switchport
This task requires domain-specific parameters to a switchport. These are: ‘Port_Name’ and ‘VLAN_Number’.
Note how the inputs flow through the actions within the workflow?
The green arrows descending illustrate the ‘success transition path’ for each action component.
So, what about these questions?
1. Is the VLAN in use?
We can be more specific here, but it adds complications to the answer. Version two is: “Is the VLAN in use in the network zone that the device Continue reading
He played a key role in moving HPE into the SDN and NFV space.
On this episode of the History of Networking over at the Network Collective, we interviewed Radia Perlman about the origin of Spanning Tree. She is really delightful, and we plan on bringing her back on in the future to talk about other topics in the history of networking technology.
The post History of Networking: Radia Perlman and Spanning Tree appeared first on rule 11 reader.
Company executives had touted its cloud business as part of its Q2 results.