Although vendor-written, this contributed piece does not advocate a position that is particular to the author’s employer and has been edited and approved by Network World editors.
Cisco estimates 50 billion devices and objects will be connected to the Internet by 2020. And that estimate may be low. If consumers count every device that draws power in their home – lamps, light bulbs, kitchen gadgets – and then factor in objects at work, there may be many more billions of connected devices by then.
But the problem is, many traditional networks are still manual, static and complex, which isn’t ideal for IoT. To realize the promise of a hyper-connected future, three shifts must take place.
To read this article in full or to leave a comment, please click here
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
In 2001, a bunch of people got together and wrote a manifesto on Agile software. There were two main factors that made the output suspect. First, the fact that they even called it a manifesto. Second, the manifesto had nothing to do with software. It talked about values.
For those in need of a refresher, here’s the “Manifesto for Agile Software Development:”
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
-- Individuals and interactions over processes and tools
-- Working software over comprehensive documentation
-- Customer collaboration over contract negotiation
-- Responding to change over following a plan --
That is, while there is value in the items on the right, we value the items on the left more.
Somewhere along the line, we started doing daily standups, two-week sprints, maybe a little pair programming here and there. Since then our software output and productivity have sky-rocketed. Remember when we used to have an end-of-project company bug hunt? How about the integration Continue reading
It's a busy day for Cisco as it launches HyperFlex, a hyperconverged infrastructure (HCI) appliance family; and announces the acquisition of CliQr Technologies, a startup that aims to make it easier to run applications across multiple cloud environments.
The post Cisco Launches Hyperconverged Platform & Acquires Cloud Orchestration Startup appeared first on Packet Pushers.
It's a busy day for Cisco as it launches HyperFlex, a hyperconverged infrastructure (HCI) appliance family; and announces the acquisition of CliQr Technologies, a startup that aims to make it easier to run applications across multiple cloud environments.
The post Cisco Launches Hyperconverged Platform & Acquires Cloud Orchestration Startup appeared first on Packet Pushers.
Networking giant plans to acquire cloud startup for $260 million.
Introduction
BGP Confederations are one of two tools a network designer has to work around the full mesh requirement of iBGP. BGP confederations are defined in RFC 5065 which obsoletes RFC 3065. This is how the RFC defines BGP confederations:
This document describes an extension to BGP that may be used
to create a confederation of autonomous systems that is
represented as a single autonomous system to BGP peers
external to the confederation, thereby removing the “full mesh”
requirement. The intention of this extension is to aid in
policy administration and reduce the management complexity
of maintaining a large autonomous system.
The other option to work around the full mesh requirement is of course route reflection.
BGP Confederation Operation and Use Case
BGP confederations work by having several sub AS or member AS that are used internally to divide the BGP domain. From the outside they all look like they are the same AS though. By breaking up the BGP domain, there will be less iBGP peerings which makes the full mesh requirements easier to handle. Do note though that it’s entirely possible to use route reflection within a member AS to combine the two technologies.
BGP confederations made a Continue reading
CliQr's 100 or so employees will join Cisco's Insieme group.
Cisco goes hyperconverge wild.
This is the second VMware exec in a week to leave for a VC.
One of my college professors has suggested that the question of whether or not Apple should help the FBI break the encryption on the iPhone used by a terrorist is an ideal diagnostic question for your view of all things privacy. There are, of course, gray area answers, like “Apple should help the FBI break the encryption in this case, but not others.” The problem is, of course, that this isn’t the simple answer it might seem. First, there are motives behind the apparent motives. Many people see Apple as just “doing what’s right to save the world.” I don’t see it that way at all. Given I’m a bit cynical (who would have guessed), I see two motives from Apple’s point of view.
First, Apple is trying to protect a marketing stance. They’ve as much as admitted this in court documents and the implied threat of suing the U.S. Government for loss of revenue if they’re forced to build a version of their O/S that will allow the FBI to break the encryption. Just Security notes—
There are other interests at stake here too. Apple has a liberty interest in not being dragooned into writing forensic Continue reading
Mirantis polishes OpenStack.