Energetic debates of what SDN is and the expanding scope of what it can do for our customers continue to race along in a chaotic frenzy. In addition, the overall SDN market is somewhat fragmented in terms of both vendor positioning and marketing. Collectively, the conversation really comes down to improving business agility and the efficiencies gained in bringing new services to market. Essentially, the goal is to enable operators to make their networks and services go much faster.
While software defined networking (SDN) technologies continue to drive significant entropy in our industry, Network Function Virtualization (NFV) recently rose up and became a key focus of many discussions at Mobile World Congress in Barcelona last month. Read More »
Over the past 2 months or so, I’ve been blogging on Cisco Domain TenSM, Cisco Service’s framework to guide you on your path to data center and cloud transformation. We are just over half way through the discussion on Cisco Domain Ten, so I thought it worthwhile, especially for anyone reading about this concept for the first time, to write a quick refresher and summary of the articles I’ve written so far. So forgive the brevity and please do dive into the links/URLs for more information if indeed you missed these articles first time. And if you’ve read every article -- thanks!
One of the most exciting things about Cisco Intelligent Automation for Cloud (Cisco IAC) is its ability to deliver the self-service agility and flexibility that a business requires to drive its success. Capacity is instantly available when needed, enabling creative innovation to bear fruit much faster (think research institutions executing millions of computations, software engineers developing new applications, or retailers launching holiday marketing campaigns.)
The benefits of cloud computing are obvious but what about the costs? For example, how do you know which resources a particular project is tied to and whether it makes good business sense? How do you make sure your users shut down services when they’re no longer needed? And how do you implement a cost model to charge back IT costs to the proper business unit or project?
These are questions that are bubbling to the surface of many enterprise cloud discussions, which is why I’m particularly excited to announce our new partner, Cloud Cruiser. Cloud Cruiser has integrated their financial management system with Intelligent Automation for Cloud, enabling enterprises to take control of their IT spending and use the granular cost information it gathers to drive better business decisions.
By implementing a financial management solution designed for the cloud, enterprise IT becomes a partner to the lines of business, providing valuable insight into the IT costs associated with the projects and applications they deploy. Chargeback gives business units the advantage of only paying for the resources that they use, resulting in both a reduction of waste (who wants to pay for those VMs that are no longer being used?) and more educated IT spending decisions, such as whether to use internal or external IT resources for a particular project. Self-service budgets and reports make users more fiscally responsible for the resources they deploy, driving costs down and productivity up.
In short, Cloud Cruiser and Cisco Intelligent Automation for Cloud work together to help enterprises make the most of their enterprise private cloud by delivering better service at lower cost.
To see how Cloud Cruiser for Cisco Intelligent Automation for Cloud works, view this short video:
Read the joint solution brief and web page to learn more about Cloud Cruiser for Cisco Intelligent Automation for Cloud.
Cisco continues to roll out innovations that will enable the next generations of multi-cloud computing. I’m a product manager working on Cisco’s Cloud Management software, and we’re all about the high-level, self-service, automatic provisioning of services that the end-user cares about. The network just moves ones and zeros, and all protocols of interest (HTTP, SSH, RDP, SQL, etc.) work fine over TCP/IP. The hypervisor takes care of putting that pesky motherboard chipset and storage bus into a black box, right? The end-user doesn’t care about that stuff, or at least doesn’t want to have to care about it.
A common perspective, except among the engineers who manage the network, is that network infrastructure is a bunch of mysterious plumbing that “just works” and how it does what it does doesn’t matter. Indeed, many vendors in the “cloud” arena would like to perpetuate this perspective on the network. They would like you to believe a bunch of dumb pipes can carry traffic and that determination of the traffic (content, flow, etc.) is determined at higher levels in the stack.
In some cases, this is true, but operating this way doesn’t unlock anything new. The model they describe would be brilliant if all of your network requirements were defined in 1998. Few companies can afford to operate technology today like they did in 1998 and remain competitive.
Cisco is announcing a newNexus 1000V(N1KV), and this one changes the game.In brief, the Nexus 1000V is the foundation of the networking services that Cisco brings to virtual computing. The N1KV can be managed using the same NX-OS commands and practices used to manage the Nexus 5K and 7K switches, and extends network control down to the VM and virtual port into which a VM is “plugged in”, even across different vendors’ hypervisors.
The N1KV is also the platform for additional L2 and L3 network services such as those provided by the vASA Firewall, vNAM, and VSG. The new Nexus 1000V InterCloud extends this ability to cloud service providers, such as Amazon, but is “cross-provider” (in fact, it doesn’t even depend on the Cloud Service Provider). For me, in my role as a Cloud Product Manager, this is an important new addition to basic networking capabilities, and is exactly the kind of thing that Cisco can and should do in its role as “Networking Giant” to open up the promise of hybrid or multi-cloud.
I have a mental image of what this can do, and I tried to put this into images to the right. Animation would have been better, I just don’t have the Flash skills to put it together for a quick blog post. I envision a virtual machine as a ghostly “physical” server tower with network cables plugged into it. These network connections can come from end-users in a client-server model, or any of our web-and-mobile constructs. After all, we still are end-users connecting to machines. Of course, the “client” for a compute function could be another compute function, so there is a network cable coming from another nearby ghost server. These ghost servers can today float from blade to blade thanks to most mainstream virtual machine managers (VMM) and a virtual switch like the N1KV, and the cords stay connected throughout. With the new N1KV, that VM can float right out of that VMM and into another VMM (such as across VMware datacenters, or even from VMware to Hyper-V), or out to a public or hosted provider. The cord just magically uncoils to remain connected wherever that machine goes! I love magic.
The N1KV provides that cable that can float after its ethereal virtual machine. It also provides the platform to maintain monitoring by the vNAM, even as the machine moves. You simply can’t economically achieve this using basic dumb pipes. Add to this the new Virtual Network Management Console (VNMC) InterCloud management capabilities. In order for that cord to stay connected, there do have to be network switches or routers along the way that understand how to make that network cable follow the machine. VNMC InterCloud manages these devices, but adds another particularly important capability: actually moving the workload.
VNMC InterCloud adds the ability to discover virtual machines, and convert them to a cloud-provider’s instance format, move what could possibly be a fairly large set of files, and get that machine started back up in a far-away environment, with seamless network consistency. VNMC InterCloud is like a puff of wind that pushes the ghostly VM from my corporate VMWare-based cloud to float over to my hosted private cloud. Remember, ghosts can float through walls.
This is groundbreaking. Workload mobility is one of those hard-to-do core capabilities required for all of us to realize the promise of multi-cloud, and it requires a network that is both dynamic and very high performing. I’ve been looking forward to this from Cisco for some time now.