This is part 2 in a 2-part series about our API-based architecture. Part 1 explains how we provide content as a service to sellers.
Federated identity is central to cloud computing. You can’t have a useful hybrid cloud service without it. Read More »
Tags: API, architecture, Cisco IT, cisco on cisco, cloud, cloud services, data center, identity, identity as a service, salesconnect
This is part 1 in a 2-part series about our API-based architecture. In part 2 I’ll talk about the advantages of identity as a service and data as a service.
Before the cloud, applications had a web interface that connected to a back-end database. Each application authorized its own users.
Today, that monolithic application architecture is going the way of dinosaurs. Cisco employees use more than 400 cloud services. So even after we added single sign-on for Cisco applications, users still had to separately sign on to cloud applications like Salesforce. Not a good use of time. Read More »
Tags: API, architecture, Cisco IT, cisco on cisco, cloud, cloud services, content as a service, data center
My final observation from my days at the London Gartner Data Center Conference is related to SDN and ease of network management – or otherwise. Hopefully this discussion will give you some ideas for good questions to ask at the Las Vegas conference, which is running as I write this.
Cisco UCS on show at the Gartner Data Center Conference
Before I start, if you are at the conference in Las Vegas, please do take time out to visit the Cisco stand #305 to find out more onCisco solutions including Unified Computing and ACI. Also take some time to say hello to our with new, exciting team members from our Metacloud acquisition – it’s fantastic to have such OpenStack and DevOps expertise in particular part of the Cisco team.
To catch up on my earlier questions, see my part 1 and part 2 blogs – questions you can ask at any SDN conference or of any vendor, since this blog series is not just about the Gartner conference. Now on to more SDN questions to ask ….
Read More »
Tags: ACI, API, Cisco UCS, cisco_services, network_management, nms, SDN
As the IETF (Internet Engineering Task Force) meets in Hawaii (IETF 91), the unavoidable question for both participants and observers is whether a Standards Development Organization (SDO) like the IETF is relevant in a rapidly expanding environment of Open Source Software (OSS) projects.
For those new to the conversation, the open question is NOT whether SDOs should exist. They are a political reality inexorably tied to trade policies and international relationships. The fundamental reason behind their existence is to avoid a communications Tower of Babel (with the resulting economic consequences) and establish governance over the use of global commercial and information infrastructure (not just acceptable behavior, but the management of resources like addressing as well). Rather, the question is about their role going forward in enabling innovation.
SDOs (like the IETF) have to evolve their processes Read More »
Tags: API, carrier ethernet, ietf, network function virtualization, Open Loop, open source, Open Stack, open standards, OSS, SDN NFV, SDO, service providers, software defined network, yang
Over the past several years, I’ve been lucky enough to be a part of two important trends in the networking industry – the evolution of open standards and open APIs, and the definition of policy as the key interface to the network.
Open is an extremely important word to the future of networking. The simple dictionary definition for open means not closed or locked, allowing access to inside, and freely accessible.
The ultimate networking environment will allow a user the freedom to connect anything together in the cloud and to an existing environment. In order for this vision to happen, companies must work together to create a common language.
OpenStack has garnered a lot of interest in the development community and among our customers. We at Cisco have been actively helping to shape the discussion around policy. Working collaboratively with our partners and competitors, we helped create Group-Based Policy (GBP), an intent-driven policy API for OpenStack.
The Group-Based Policy initiative represents a significant innovation in how users conceive, manage, deploy, and scale their applications in OpenStack clouds. And its now available as a 100% open source solution available to any vendor. When coupled with Cisco Application Centric Infrastructure, we are able to offer our customers a completely policy-driven network.
Read More »
Tags: ACI, API, APIs, application centric infrastructure, Cisco, Cisco Application Centric Infrastructure, cloud, data center, group-based policy, network, networking, Open, open APIs, open source, open standards