Container networking and storage is hella-complicated. Check out this conversation with Usha Ramachandran, Richard Seroter, and myself on the topic, including a discussion of why it’s so complicated and how Cloud Foundry addresses the problems.
Since being tapped to lead Cisco in 1995, Chambers has grown the company from a $2.2 billion hardware manufacturer to a $48.6 billion network hardware, software, security and services powerhouse that’s more bullish than ever on becoming the world’s No. 1 IT company. Cisco had 3,827 employees when Chambers was appointed CEO. Today, there are more than 70,000.
Also, a somewhat random DevOps callout from a senior executive:
“We are going to move the entire engineering organization to a DevOps and an Agile development model,” Lloyd said. “That’s hard work. But, in many cases, it’s a different way of doing things that will allow us to do things quicker, faster and much more customer-centric.”
And, on whatever InterCloud is, perhaps “EverythingCloud”?:
“Intercloud is a step beyond a public cloud,” Chambers said. “Think of Intercloud as Cisco services delivered from a cloud: hosted communication, security, collaboration. Think of it as our customers’ private cloud capabilities. Think of it as our partners’ and Cisco’s architectural implementation of this, if you will, in terms of our partner clouds. And think of it in terms of a public cloud.”
P1030364 (by david_terrar)
In many ways, Neutron’s failure and planned rebirth are a metaphor for OpenStack as a whole, with the tech promising too much at the start, becoming overly dependent on vendors, and only being fixed when paying punters started to confront its weaknesses. As the OpenStack collective learn these lessons the hope is that they will run into fewer errors, and perhaps make good on their plan to provide a viable cloud operating system to telcos and other businesses.
[L]ess than 30 percent of the 321 IT professionals surveyed have deployed or plan to deploy SDN in the next year. Add on another 40 percent that have no plans to implement SDN at all.
Why can’t you just pay attention to my main ideas and ignore the details?
“It is clear that networking has for a very long time been a black box. They don’t even come with APIs,” he explains. “This is the history that forced us to really look at way networks are laid out and build [devices] and do [it] ourselves. Also the cost – everything else in our data centre [is] more efficient.”
Stacey Higginbotham takes a crack at explaining why Cisco’s announcement this week is a big deal for SDN, and Cisco:
> Cisco saw all of that play out and doesn’t want to find itself in Dell’s or HP’s shoes. So it is focusing on becoming a control point in the emerging virtualized stack and putting greater emphasis on software.
And, explaining what Cisco’s, well, ethos here may be:
> The networking world of old said it cared what the application wanted, but the application had to speak network’s language. So the application had to figure out if it needed more bandwidth or was experiencing latency issues or whatnot.
> But when the application comes first, this means you offer the application (and developers) a way to see how the network affects your application. So if something breaks, the developer doesn’t have to go looking for the networking code book to describe the problem because the networking infrastructure and software does the work.