 Welcome everyone. Thank you for attending this afternoon's session. I wanted to just spend a little bit of time talking through a major transformation that Cisco has been undergoing over the last six months. We're kind of at the beginning of the journey and so there's a lot of information in here that you know we obviously haven't learned all the lessons yet but as we go through this journey we're learning a lot of lessons and I want to kind of share some of those with everyone. And so just kind of an outline of what I'm going to be speaking to. I want to kind of talk a little about what's happened in the last six months at Cisco, the transformation we've been going under. Explain what I mean by application-centric. You're probably thinking that it's a trick, right? A networking company like Cisco talking about applications but it's kind of explain what I mean by application-centric. Talk a little bit about the InterCloud. It was announced at the Cisco Partners Summit about a month ago that we're building this InterCloud and so I'll explain a little bit about what that is, how that fits into the journey we've been on and then kind of wrap up specifically on what we're doing within OpenStack and how we're contributing to the OpenStack projects. And so at the beginning of our journey was a little bit different than you might have expected, right? And so Cisco has been looking at you know has been supporting cloud and been in cloud providers and enterprises doing private clouds for some time, you know, a couple to three years now, create reference architectures and many of you may have even developed or deployed your cloud on a Cisco reference architecture and so as we looked at what was happening within the industry it became very apparent to Cisco that if they didn't change the big box mentality and start looking more at how to deliver things as a service then it was going to be a different company in several years and Cisco and the environment that Cisco was in may be a lot different for them and they may not succeed or be successful in that new environment. And so we wanted to kind of create this sense of urgency and so when you want to create a sense of urgency and this is important for all of you in the business side of your corporations trying to make a transformation to a cloud. The first thing you have to do is kind of realize that it's not just about the technology. Everyone here probably loves technology like I do but it's really more about the people and the processes around what you do every day right and so in order to kind of change from the direction you're going in a certain you know you're going down a certain path with your application development you're going down certain path with how you manage and run infrastructure. What cloud is doing is kind of changing all of that and to kind of get a sense of urgency around the need for that change. You have to look at how you're doing your organization and how your organization is set up to support cloud services and cloud applications. And so you kind of look at the operation of your environment you look at how you're doing your development and your test how you're going to take things into a CI you know continuous integration continuous and development type of environment. A lot of your processes that you're using today don't really map well to an agile CI CD type of framework and so you have to rethink how you kind of go from development to unit tests to you know production and to you know quality of you know QA if you have a QA process in there somewhere right and so trying to figure out how you transition from the developer to the production side is a much more quick process today it can take minutes instead of you know months like it used to take and so looking at how your processes need to change to support that and then from a technology standpoint a lot of things that are not thought about are sort of how that user experience would be and some of the orchestration pieces that are needed to really orchestrate your end-to-end service. How do you make sure that that service is highly available or that that application if something goes down that supports that application that your application data can migrate seamlessly to another environment that keeps everything up and running for your users. The other thing that's kind of happening at the same time is everything is becoming more commodity and lower cost right cost is a big factor for especially an open stack type of solution and so you have to look at how does that impact your applications how does that impact your time to market and your availability of your services and then the other thing to keep in mind is that a lot of a lot of the technology impacts are slow and take time to make changes there's a lot of investment in existing infrastructure existing components within that infrastructure that you can't just rip out and throw in brand new commodity gear and so trying to look at how do you make that transition is important right and so part of the sense of urgency that Cisco had was you know cloud is basically changing IT as we know it and so part of that is the perimeter is pretty much gone right most of us are using cloud in different ways today and planning even think about it as a cloud right most of us have mobile phones and we're doing things in the cloud all day long with those the data center is changing it's not the same type of silos that you have today or it won't be in the future right if you're not changing the way you deploy data centers and manage data centers you will be because it's completely different or it will be completely different in the next few years the way that people want to consume information and consume and environment has changed to be more of a consumption model people really just want to pay for what they're using they don't want to sign a long-term commitment anymore and so when you're Cisco and you sell everything as a big box and you look at a you know one to three year term typically a consumption model is not something you really adopt very simply and easily right and so we had to kind of look at how does cloud change the way we need to be selling our services and our products and then when we think about the software development lifecycle as things that move from from waterfall to agile dev ops and and the likes of dev ops and capabilities around dev ops are becoming more and more prevalent and in every environment and so we think about how that changes the way you're developing your applications and using the environment you have to kind of understand how those impacts are going to be on your organization and then once you kind of kind of put this sense of urgency and get people sort of understanding why you need to do something different you then have to kind of organize to be successful part of that organization is you know in Cisco's case we created a cloud board and their main job was to sort of look at how does Cisco evolve from where we're at today with traditional applications that require services and you know six to nine months to turn up to you know software as a service type of solutions that just you deploy from an environment and it runs and turns out very quickly there was an advisory board created to sort of look at how do we create this organization how do we govern this organization and then we wanted to you have to kind of make sure that you're enabling the change agents within your organization to make that change because it is a big change and a big shift and then lastly once you do that you want to innovate and allow that innovation to kind of sponsor innovation if you will so this small group of the cloud board sort of sponsored innovation across all of Cisco the second thing they did was they sort of identified some big strategic opportunities and they selected some strategic initiatives to kind of help get some quick wins and drives for quick successes and so within Cisco we took WebEx and have sort of made WebEx a cloud-enabled solution today that's running on on the Cisco cloud we've worked with our partners in the telco space and in the ISV space and creating partnerships and deploying services across partners and sort of this inter cloud model and then we you know basically made a decision that we're going to move with agility and speed that Cisco hasn't had since the early days when they were a startup and so we've kind of turned a corner now and a lot of what we've been developing and what I'm sharing today we are in a very agile very quick deployment type of model we're releasing code every couple of weeks and applications like WebEx make change hundreds of changes a day and no one even knows it they're very agile inside this cloud environment and then the last thing they did was they started recruiting bringing people in that have built OpenStack clouds to understand applications running an OpenStack that have worked in in different environments in the valley to understand the need for agile and the need for developing with speed and agility and then they started removing any barriers that came up from within some of the business units within Cisco. So that's sort of how you know Cisco started that in the beginning started to make this transformation and make this change. The application centric piece came in from a standpoint of it's really about the application right and Cisco had a hard time kind of getting their mind around it's not about the network it's really about the application the network has to support and do things that help that application perform better and to to get from point A to point B but it's really about the application and so part of what we tried to do was enable the innovation within the applications that were being developed and ported into a cloud within Cisco to give them the skill that an OpenStack cloud can provide and to give them the ability to innovate very quickly within that cloud. We started connecting our developers within Cisco to the different services that we can enable within the cloud and what's really interesting about this process is that as our business units started working on our cloud they started talking to each other about what they're doing in our cloud and they started saying oh we could if we we all use this service so if we just put the service into the Cisco cloud we could all just leverage this service and not have to create it and maintain it ourselves and so that by kind of enabling your developers to think outside the box they can start bringing ideas back into your your organization to do better things for the developer community which then turns into more ideas so it's kind of a it's a good practice to get into that and then from an organization standpoint we kind of have been looking at our customers and how do we help the IT departments of our customers you know kind of transform into more of a business unit instead of a cost center and so you know for a long time IT has had this kind of perception about them that they're a cost center that they're slow to change and one of the things that we're trying to do is enable them to be thought of more as a business unit and not so much as a cost center and then the last thing that we're doing is we're kind of creating this exchange of application marketplaces and so it's it's pretty clear that the one of the main use cases for cloud is obviously deploying quickly leveraging existing applications where possible and so one of the things that we've done is kind of provide this exchange of application marketplaces. There's a reference architecture that we just put out called CRA version 1 customer reference architecture and it kind of shows the different layers of you know the Cisco cloud and services components. It's based on you know Cisco UCS Cisco networking obviously but it also integrates with our partners in the storage area you can see NetApp and EMC there. It also integrates with some of our partners in the orchestration layer so we have you know both VMware and Canonical and Red Hat type of partnerships and we kind of break it down into different services layers and the service management and the application the automation of these these cloud components underneath that. So that's kind of the the transition to being very customer you know being a very application centric right thinking more about the application. With that journey we've kind of looked at what does Cisco do to support this application transformation within Cisco. So what does the Cisco need to do to enable this? So the first thing I kind of ask is why why is there an inter cloud why do we announce inter cloud and so the original goal with with this cloud services team within Cisco was to kind of enable the Cisco business units to develop and take the traditional application approach and kind of transform that into more of a cloud either cloud native or at least cloud ready or cloud capable type of a SAS model. But to accomplish that we realized that and this was realized you know six months ago that we had to build and operate a cloud to really understand how to enable applications in a cloud. And so part of that meant that we had to kind of look at a new consumption model that was evolving with cloud and so if you think about the product business units within Cisco they all have different ways that they like to sell and bring their applications to the market and so we had to work very closely and understand kind of what are the consumption models of our users and how are they buying applications and services from Cisco today. We then had to kind of talk with customers and understand how our customers are consuming services today and how they'd want to consume services in the future and we had to work with our partners to see how we can help bring them along this journey with us. And so at a very high level the Cisco cloud strategy is kind of these four components where you have the existing enterprise private clouds and many of these clouds over time may go away but today we still have a lot of private clouds out there. You have partner provided clouds a lot of Cisco powered clouds in the environment out there. There are different public clouds that are not necessarily powered by Cisco but are still you know used very heavily by consumers. And then there's a Cisco cloud services piece that we tried to build internally to help bridge the gap between where our customers and partners are at and where enterprises are at today and trying to move them into a cloud transformation. And so if you think about that enterprise private cloud piece you know you really have things like you know the enterprise workloads and some big data capabilities that we wanted to provide to them. There's a suite of collaboration and video services that Cisco runs that we want to try to make easy to consume within that enterprise private cloud space. As you go over to the Cisco partner powered clouds you have you know different types of hosted exchange services. You have different types of infrastructures of service and platform as a service players and you have things like bushel desktop as a service and DR as a service being offered by different partners. On the the Cisco cloud piece obviously we wanted to try to bring a lot of our applications and services into this environment. So kind of bringing things like WebEx and Marocchi and different security applications into the space. We partner with SAP so bringing like a HANA as a service and different types of Cisco, NFV as network function virtualization components into this environment. And then from a public cloud standpoint we wanted to be able to kind of interconnect the the partner Cisco partner clouds the Cisco cloud and enterprise private clouds to the the public clouds that a lot of developers are already using and not trying to force developers or dev ops to move or change their process which is just kind of interconnect all of this together. And that's kind of where this inter cloud name came from is we're not trying to replace clouds we're just trying to interconnect them in a way that provides you know security some network performance and network policies and and provides this inter cloud fabric that allows workloads and applications to run in kind of a heterogeneous environment. So to kind of go down to the next level of detail you know this this whole cloud in a box concept is where I've been kind of calling this where Cisco is just providing sort of a black box to our partners and and to our enterprise customers where they're able to kind of manage who they want to connect to it through the federation components they're able to get usage and billing data out for their tenants or for the businesses that are using this environment and they're able to provide service assurance and we have the API is underneath that that we're just exposing the different open stack components I'll show you in a minute and being able to provide multi-tenancy and some of the network policy assurances and compute performance capabilities while at the same time providing commodity compute pricing for the service. So from an architecture framework standpoint you know we have this infrastructure component and the infrastructure component is is very much like you saw in the customer reference architecture where you have you know the data center facilities could be any any partner any any co-location spot or any Cisco data center that is running the Cisco cloud in it and it could be any you know enterprise data center it doesn't we're not forcing anyone to use a data center of any type. The network to compute and the storage obviously run better if there's Cisco solutions and the Cisco cloud is built with the Cisco solutions but we have partners that are providing the capabilities that plug into this as well. Above that are the services layer that are all open stack and all open source components and so that you know a big key with all of this is we're supporting you know open source openly and outwardly at Cisco and not trying to bring proprietary protocols into this. Above that is the APIC which is our application policy control component for the application enabled infrastructure and policy management components to build into that and the inter cloud fabric obviously ties into that policy to allow you to kind of have control over where you move your workloads. The next layer up we call this unified platform and it has some of the infrastructure components that kind of infrastructure orchestration and management components it has some analytics pieces and it has a services platform and so from a cloud standpoint we kind of provide the fulfillment and the assurance monitoring pieces out of that out of that unified platform. We provide brokerage capabilities to allow you to kind of select which partners you want to be able to broker with and connect to the some of the BSS components like billing and entitlement and the service catalog sits in that layer and above that we have this foundational PAS environment that lets the developers connect their IDEs that they develop into into this cloud environment. The next layer up is sort of the services platform piece that has some API management and API governance capabilities. It has some of the design runtime or PAS runtime type of environments data as a service capabilities some of the app integration data visualization pieces that are needed for doing big data analytics and then some of the operational analytics to help run and operate the cloud more efficiently. And then the layer above that is sort of this app marketplace I alluded to earlier that allows applications from our partners to be inserted into our application catalog and then our partners can select which applications they want to expose to their users and their tenants. The sort of this layer above this that I don't usually talk too much about but it's important because a lot of our partners want this portal interface or the single pane of glass that lets their tenants kind of see all of their deployments across all of the different into cloud environments. And so being able to kind of provide a single interface that lets you see your private deployments, your public deployments and your Cisco cloud deployments all from one control pane and create policies and manage your workloads from there. It's sort of the vision we went after with this. And obviously above that you have the different applications that Cisco is developing that are running in this environment that our partner and ISVs are developing that run on top of this. And then over to the left you have what you'd expect from Cisco our services pillar where we can provide different services from professional services to manage services to consulting services. So then when you kind of look at what's the service architecture and this is sort of the piece that talks a little about open stack here. And so at the very bottom of this picture you can kind of see the operations piece of the Cisco cloud. We're providing you know within that black box is what this represents that I showed you earlier. So we're providing all of the monitoring all the management all the orchestration pieces. We're exposing the heat API so you can create templates or import templates. We allow you to integrate with you know Puppet or chef or whatever your choice of you know orchestration tooling is. On the right hand side is sort of this the physical environment which again I kind of mentioned the Cisco UCS B series for the compute layer and C series for the SEF and an object store layers. Above that infrastructure is where sort of the tenant VMs would be running as part of an isolated network segment. Above that is sort of that infrastructure service platform that I was alluding to earlier that shows sort of the different open stack components that we're exposing and some of the services that are exposed out of that API gateway to the pieces that we talked about above that are sort of external consumable APIs that our customers and tenants can leverage. So then when you knew the last piece of this was sort of what is Cisco doing with open stack. And so I think the first thing is that open stack has come a long way for those of you who are in Portland last year and kind of saw half of the attendance that's here and the marketplace out here was maybe a quarter of the size in Portland. You can see there's a lot more adoption going on a lot more interest in open stack. But it still has a way to go. And as we started developing and building out the Cisco cloud and deploying the Cisco cloud, we started seeing some areas that needed some additional hardening. Some of the areas that we're working on are in performance improvements. And so two of the main areas there are identity management or keystone and the messaging and message queue capabilities. So to make them more robust, to try to not have as many errors with authentication and to provide more options in terms of the types of data storage you can connect to. Ice House has done a lot and there's a lot of contributions in Ice House. So Ice House has done a lot to take us forward, but there's still more work to do that Ice House still hasn't covered in the identity piece and messaging piece. The second area that we're contributing to is some of the metering improvements. And so there are some scaling issues we ran into with Solometer. We wanted to look at different services that open stack exposures. We wanted to add those services to Solometer and there were some limitations on what we could monitor within some of the service sensors. And then there's kind of a little bit of an open security bug in my mind of how you can allow, you know, if you don't throttle, there's not like an automatic throttling of events, you could actually overload. And we have overloaded those API endpoints and kind of brought down this monitoring service because it got overloaded with events. And then from a network improvement standpoint, we're doing a lot of work today within Neutron and within both Open and Open Daylight, which is a different organization that they're partnering with OpenStack and collaborating with OpenStack around application policy control and application enablement within the network layers and then IPv6 support within OpenStack. And then the last piece that is important is in order to really have high availability and run, you know, your service at 100% uptime, there are a lot of things around the service assurance piece around, you know, API hard beats and checking the services and ensuring the services are highly available and up. And then some of the image management pieces we ran into different sorts of weird corner cases with trying to support different types of images and different sizes of images being imported. And so with that, I want to thank you for your time and open up for questions. If you have questions, there are two mics up here. They asked us to use those mics for the questions. Okay, I guess I'll just ask one. As far as the additional contributions to OpenStack, is there any, I guess, not necessarily formal documentation, but is there any way where we as a community can go to kind of view these contributions or, I guess I'll just stick with that. Yeah, there is. I can get you the location. Okay. All right, thank you. Well, thank you all for your time.