The Cisco Process Orchestrator has very rich integration capabilities, yet we often hear the question, “Does it integrate with…” or “Does it work with” [insert product]. The Cisco Process Orchestrator is a primary component in the Cisco Intelligent Automation for Cloud management solution.
The fact is that in modern environments with modern orchestrators the answer is always yes. The reality is that cloud automation requires a Process Orchestrator tie into a variety of different systems in order to start offering cloud services. Remember, Cloud is an operating model, not a product. This means that to deliver self-service, on-demand services requires all the elements of the service be orchestrated.
Cisco’s internal private cloud is one such example.
The graphic below shows the components in the deployments. You see integration with Cisco UCS, VMware and storage, as you would expect. It also orchestrates IP address management (that IP won’t provision itself), Remedy incident, CMDB, ActiveDirectory (so tenants can log in), image management and a few other things such as Service Assurance.
By the way, the architecture below is Cisco Process Orchestrator provision across multiple Cisco data centers.
Read More »
Tags: CIAC, Cisco Intelligent Automation for Cloud, CiscoIAC, CITEIS, cloud, Cloud Computing, data center, IAC, integration, intelligent automation, orchestration, software, unified management
This blog is a follow on to my introductions to onePK and the onePK software architecture. This post is special, as I have the pleasure of introducing, by way of conversation, my colleague Shelly Cadora, an experienced speaker on SDN, and developer with onePK, and to highlight some of the work she has done with onePK.
“So, Shelly, in my blog on onePK a few months ago I said that I thought that we would start to see new models for network management and deployment enabled by onePK. Lo and behold! You created just such an example for demonstration at Cisco Live, so what’s that mean for us all?” Read More »
Tags: API, application networking services, cisco live, Cisco onePK, network management, onePK, process hosting, programmable networks, SDN, simplify deployment, software
In the months since I attended the Smart Cities event organized by Qualcomm and CommNexus in San Diego, the buzz about “Smart Cities” and the use of machine-to-machine (M2M) wireless technologies has only grown louder and more intense. Which Smart City-relevant innovations are under development inside Qualcomm?
Known primarily for mobile chipset technologies, Qualcomm is working to optimize wireless networks and sensors that support M2M solutions and, ultimately, Smart Cities of the future. An often-overlooked part of this initiative is the company’s work in preparing the wireless industry for the imminent tsunami of data that will come when countless “things” equipped with M2M wireless sensors—part of the “Internet of Everything”—hit wireless networks. Qualcomm calls it the 1000x Challenge, referring to wireless industry predictions about a 1000x increase in mobile data usage between 2010 and 2020.
Last month, Qualcomm Executive Vice President and CTO Matt Grob presented at Meeting of the Minds 2012 in San Francisco. His presentation, “Next Big Innovation: The Mobile Internet Transformation—Meeting Network Capacity Needs of Cities,” showed how wireless connectivity is revolutionizing the way people live and interact with each other in cities.
A few examples of Qualcomm tech in this arena:
- From Qualcomm’s perspective, a “smarter grid” employs digital wireless technologies that allow utility companies to safely and securely deliver prepaid electric services that save homes and businesses money through real-time monitoring of power usage over existing cell networks, thus reducing deployment costs for the utility and saving energy for the planet. At the same time, smarter grids enable customers to better manage their own energy usage.
- One recent Smart Grid example is Qualcomm’s work with Duke Energy, the largest electric power holding company in the United States. The success of this collaboration has enabled Duke Energy to install hundreds of thousands of communications nodes, which interface with electric and gas meters, line sensors, transformers, and other end points, meters, sensors, and distribution automation equipment, and optimize energy usage in five states.
- Working with ECOtality, a maker of electric vehicle (EV) charging stations, Qualcomm participated in The EV Project, the largest deployment of electric vehicles and charge infrastructure in history. The project, now in nine states plus the District of Columbia, leverages cellular technology incorporated into charging stations, enabling EV car drivers to easily find charging stations with their smartphones. Moreover, the solution allows users to reserve stations as well as receive alerts users when the charge is finished or if it the charge has been interrupted.
- Another exciting development, also involving EVs, is Qualcomm Halo’s teaming with Renault and Delta Motorsport in London. Qualcomm Halo, a subsidiary of Qualcomm, produces wireless charging mats that enable EV drivers to simply drive up and park over the charging mat—no exact alignment necessary (e.g., you have to line up your electric toothbrush perfectly on the charger in order for it to charge). Initially, the benefit is no longer having to deal with tangled charging cables. But looking beyond that, Qualcomm Halo envisions embedded chargers in the roadway. Even further out is the idea that these mats could be built into the road and connected to the overall Smart Grid. Depending on the time of the day, more or less energy resources could be devoted to that specific roadway, effectively channeling energy to where it’s needed most.
Cisco IBSG is also engaged with the Internet of Everything in a variety of ways, such as through the Connected Vehicle.
I’m interested in hearing your thoughts on how M2M connections—and the Internet of Everything—can enable Smart Cities of the future.
Tags: Cisco, connected vehicle, IBSG, infrastructure, Internet of Everything, IoE, living lab, M2M, Machine to Machine, Networks, services, smart cars, Smart City, Smart Grid, software, wireless
Enterprise trends driving SDN and Network Programmability are becoming clearer. The skyrocketing number of virtual/cloud devices is making human configuration infeasible. A natural result will be that networks will move from being integrated based on physical box boundaries to being integrated based on software boundaries. Put another way, traditional box based network integration will be overwhelmed by device proliferation. Therefore businesses must adopt new approaches to device configuration and control. This will include a new layer of network software which will instantiate, orchestrate, and dismantle virtual networks.
But what does this really mean? Read More »
Tags: API, Borderless Networks, Cloud Computing, controller, Enterprise, intent, interface, onePK, partner, SDN, software, virtualization
In my prior blog entry, I answered the first of Durga C.’s questions to me. Here’s all three of his questions:
- What is the role of the hardware in an RDMA transaction? In other words, why does one need special hardware (e.g., InfiniBand, iWARP, RoCE, etc.) hardware to do RDMA as opposed to a “normal” Ethernet NIC? (see prior blog entry)
- Further, can you explain why pure software solutions (e.g., Open-MX) are better than nothing when you don’t have hardware support?
- Also, what is the difference between “RDMA” and “RMA”?
Let’s explore the last two of those questions. Read More »
Tags: hardware, HPC, mpi, RDMA, RMA, software