 First, we're going to kick it off with a keynote from HP. And to speak to us this morning, we have Biri Singh, who is the Senior Vice President of Converged Cloud and the GM of HP Cloud Services. So Biri Singh. Thank you, John. Appreciate it. Thanks so much. Good morning. How are you all doing? Great. Thanks for taking the time out and joining us here. Before I get started, actually, I think we all owe a round of applause to Jonathan and the OpenStack Foundation. They've done an admirable task in the last few months, some great progress. Setting up things like this is never easy. You've got to balance true community. To me, it's all about transparency. And I think they've done a fantastic job. So I want to thank Jonathan and the Foundation's efforts. We've got a lot, learning a lot, lots more work to do. But I think it's off to a fantastic start. So again, thank you. I'm going to spend some time with you this morning on talking a little bit about how HP is thinking about the cloud space, give you an update on what we've been up to, but try to frame it around what we think are the challenges around really getting to a true open, scalable, interoperable cloud, and an ecosystem around it for the enterprise. And by that, I mean the enterprise production workload. And so I want to talk a little bit about what we think about it, what we're learning. We've been active here now for a couple of years and hope to share with you some insights. And we'll go from there. So I've shared this slide before. The way I want to talk about this is we've all experienced this. We're living this real time. The notion of mobile and social, big data, analytics, all coming together with the cloud, to me, is an obvious thing. But I think it's one of the most disruptive, if not the disruptive phenomena over the last 40 years. And as long as I've been involved in IT, which is a good chunk of those years, it's definitely something I think is the most disruptive piece. So how do these things come together? And the way we've thought about it is really trying to lay it out in these four, actually five points. So the device, the front end, is how we interact with all of the information. Our identities, our lives at home as consumers, as well as increasingly at work, are all essentially in the cloud. So a safe identity with all of our information accessed through the cloud. And the cloud becomes the back end. But really what's happening now, and we've noticed this largely through the change in our experiences in the social media, social network side, is we're not interacting with this information and our devices, laptops, smartphones, what have you, the endpoints, many devices per individual. And we're really starting to experience a very different type of interaction, and we're getting things done. In the old legacy traditional view, you had a view that systems of record were the capture control points. And typical, for example, ERP systems were systems of record. They were control points. They have been control points. Now what's actually happening is through bite-sized applications and services accessible through literally anywhere, we're starting to move towards more a system of experiences. So we're layering on a bunch of intelligence, a bunch of work, a bunch of much lighter web-based business process and applications and services to get things done. The devices now become a get it done device. And so many devices for all of us, cloud becomes the back end, lightweight interactions between the devices, and not just machine, but also the machine-to-machine element of it generates a huge amount of data. And so analytics to make sense of it all. And then the last point I'm going to come back to a little bit later is this whole idea of taking to bring your own device phenomena, which has been the last three, four years, now unleashed itself onto the enterprise, and it's a whole new style of IT that's got to take it on. Getting that whole phenomena together and tying it securely in the enterprise is something that is critical not just for mobile and how that will unfold, but also true production workloads from the cloud actually being part of an everyday experience. It's boring after a while to just deal with email or some lightweight apps. You actually got to work in a way that you actually get things done in the work environment as well. So that's how we framed it. Fairly obvious stuff, but for us it was a good guidepost to say we've got to look at big trends and see how all this comes together and how does this shape sort of HP's point of view. And then we think some implications for what we're all trying to work on, which is to build a truly open ecosystem of a world-class sort of cloud platform. So I think it starts with a concept in terms of getting to the enterprise, this idea of hybrid delivery. And the way I want to frame this is we all talk about hybrid clouds. I for one don't like the term hybrid cloud. We don't use it. We think it's better to sort of think about it as hybrid delivery. Customers have hybrid environments, have hybrid clouds. As an IT vendor, it's our job to actually manage and deliver a set of solutions, cloud solutions across different environments. So the way we frame it is there's sort of the traditional, virtualized environment, private clouds, public clouds, and this idea of sort of managed or hosted clouds in between where essentially it's a CAPEX, two OPEX transition as far as the customer says they say, I don't want to sort of set up my own private cloud. I'd like someone to have it managed for me. So against that backdrop, delivering a set of services or a set of experiences for customers that essentially want to build their cloud environments, infrastructure level, application level, data, big data analytics level, as well as just consume out over the internet or out over your dedicated cloud environment, you got to sort of balance the needs of that. So hybrid delivery, what we've been focused on is the ability to be able to stand up, not just private cloud environments, public cloud environments, and then run them for on behalf of our customers, but also do it in a common shared way. So increasingly, there's a need not just to be able to deliver across this, but be able to kind of deliver, quote unquote, one stack across these environments. And that's a key part of what we think is going to drive adoption going forward. Let me talk a little bit about the public cloud space. It's been a very active space. If you look at it, certainly startups and developers around startups, certainly SMBs have been quite well served. There's some major players in the space. And the way that, I think that market is, if you actually look at the startup world, I would say 80% penetration has occurred. Most series B startups and above are essentially running their infrastructure for the most part in AWS, right? And I think that whole market, the way it's been defined really caters to the notion of sort of startups, media workloads. There's a lot of sandbox IT going on, but we're not seeing heavy scale production workloads out there yet at scale. And there's been lots of talk. There's been obviously lots of active conversations about what that means and what does that look like. Now, if you look at the startup and you look at the SMB space, there's a certain amount of spend there. But if you actually look at enterprise production workloads, it's probably 10, 20 times that spend. So if you actually do the math, we're talking about a very sizable opportunity. And really a lot of those dollars have essentially been parked. If you think about infrastructure spend post Y2K, there was a freeze in 2003. There was another freeze in 2007. We're going through yet another one in the last year. And there's been an enormous amount of backlog built up. Core infrastructure upgrade, core application transformation, traditional apps, and a bunch of new apps. And what's happened is in the last five years, the bring your own device phenomena has essentially sort of been a proxy for a bunch of spend. And I call distracted spend dealing with mobility. But core infrastructure spending, core transformation of data centers, next generation data center, cloud enabling data centers, cloudifying your infrastructure, your application level, your database, your sort of analytics layers are still a work in progress. And our contention is there's still many, many dollars essentially sitting on the sidelines waiting and watching to see what sort of happens. So there's a lot of interest in our work here. When I say our, I'm talking about our open stack community and what we're trying to get done. And I think it's critical. The next phase of this for us has to be how do we sort of make it real, right? There's been a lot of chat. There's been a lot of good ideas, lots of framing. We all as vendors have our own parallel universe of presenting cloud frameworks. But at the end of the day, it's now about getting to production workloads. So I think it's super important to think about what's happening in the public space. There's been a lot of adoption and sort of classic sort of new, new mobile web 2.0. All of the new cool things are essentially moving to cloud environments. They'll be developed with tools in the cloud in PaaS environments. They'll be running in a cloud environment over time in a trusted cloud environment. The question is how do you now tie that back to the traditional workloads that are sitting there. So that brings me to a point about talking about how we see cloud workloads. And again, this is reasonably well understood, well out there, but we've sort of broken it out and we think of traditional workloads, ultimately, that have been typically under the virtualized environments. You get to 70, 80% of a virtualized environment. You're managing clusters of VMs very different from setting up distributed cloud apps or services. You now have to deal with things like availability zones and a different networking model and a different sort of distributed model. Your apps actually have to be designed for failure. Developers have to think about designing an application or set of services around an infrastructure that'll be up or down. And that's been something that's sort of taken hold of the mobile space and a lot of the consumer side, a lot of the sort of web 2.0 space, but it's critical that we can lead as an infrastructure and a platform and a cloud OS community that it's critical that we be able to tie these things together. So a big part of our focus is what are the requirements that bring workloads reliably to run on a cloud environment? And not just public cloud, it really has to be a public, private cloud. Again, hybrid delivery, the CIO of the enterprise is really interested in making sure that they can consume these services across all delivery models, right? So if you look at workloads, they've typically been web 2.0, mobile, cloud, centric workloads, easy adoption. They've sort of gotten out there. A bunch of the companies here, a bunch of us are already familiar with that. The DevTest model has been out there. It's well understood, but now how do we move it from DevTest to production? There's all kinds of storage solutions out there. I think there's a ton of innovation going on in terms of the use cases, as well as all levels of infrastructure and innovation at the infrastructure and hardware and basic storage IP, phenomenal work going on as we speak. But then once you start getting into sort of these apps that are built for sort of reliability and are built on a certain infrastructure assumption, how do you now plan that and marry that view along both a private and a public cloud view? A lot of customers we've talked to have given us a point of view that say, hey, we want the web scale of a public cloud environment. We want an open stack like environment, but we also want all of the enterprise quality of service elements, security, performance, reliability, DR on and on. So how do you sort of marry that too? So we've tried to spend our time really figuring that out. And we've launched the HP public cloud. This past May, it's been in public beta now. We're launching several services and we're literally trying to learn as much as we can as we assemble sort of a common point of view for how do you bring private and public together? So against that backdrop, this view that cloud workloads have to now be running across really multiple delivery points. My view is SLAs and orchestration are kind of the two things that really matter. And what customers really want is an integrated experience around management and this notion of enterprise grade quality of service. So what do we mean by enterprise grade quality of service? An SLA that you can stand up and it's real. It's got real teeth. Customer service goes without saying, it's sort of a default and lots of best practices there. This notion of a secure cloud is really important. And I think getting that point across to a CIO and a chief security officer is there's a lot of work to be done there. There's not that many IT vendors that have been able to lay that out in a reasonable way. We're certainly trying. We rolled out what we think is a fairly aggressive SLA. You can go check it out at hbcloud.com. We think it's one of the more progressive SLAs in the environment. But I think the idea of standing up and delivering quality service is one thing. The idea of orchestration is, I think, yet another. And when I say orchestration, I mean orchestration with a big O. Meaning you have to deal with setting up service provisioning, cataloging, and enabling and deploying bare metal, but also above bare metal VMs and complete lifecycle management of VMs. But above that, a set of application level services at the platform level as well. So how do you, when a developer, whether at a startup or an SMB or an enterprise, is writing an app, she or he only cares about that runtime, right? And the database that's tied to it. Oh, that's what they should be thinking about. They shouldn't have to worry about auto scale or load balancing or identity or security or a set of services they want to provision to. So being able to sort of tie those together elegantly and offer that as an integrated view, not just for the developer, but in the enterprise for the IT ops side of the house. This sort of parallel sibling organization that's got to manage all the infrastructure that the CIO counts on for control points as they're seeing a whole bunch of sort of loss of control out to sort of line of business and application owners. The IT ops folks are critically involved as part of this equation. So delivering orchestration across that, I think, is vital. And I think one of the challenges we have to take up, and certainly HPs, we're spending a lot of time trying to figure it out and get it right, is how do we drive this view together? How do you drive reliability and predictability with an SLA and how do you tie it together with an orchestration layer that ultimately gives you what we call a true cloud management points of view? Now if you look at this conference here, we've had some great announces through some of our partners and some of the companies here. There's been some cool things around networking, some great alternatives around networking were announced. There was, I think, some good stuff at the platform level. There's a great compute piece that added on to one of the announces I saw. So I think there's a lot of work being done, but at the end of the day, the real measure is ultimately production workloads and how we're doing against that. And that's, I think, a key part of it. So my one challenge to all of us, and certainly HP's thinking about this, is how do we get real about this and how do we sort of focus on really production, true web scale grade services on a global level? And then what's sort of the environment in the ecosystem to go drive that? So that's my point in terms of orchestration. So when you think about design points across the board, web 2.0, all the way out to true enterprise, traditional legacy environments, I think orchestration and SLAs and tying those together is something companies have to figure out. And certainly we're spending a lot of our time figuring that part of it out. And over time, as I said, there will be a common cloud OS or platform model emerging. I think that is our challenge. I think that is the open stack opportunity, right? And this idea that a common stack, a common architecture, can now meet the needs of a multiple delivery model on a global basis at web scale and enterprise grade quality of service, I think is the opportunity. And that, by the way, folks, is hundreds of billions of dollars of spend, not six billion or 10 billion, which is where I think the current public cloud market is, for example, best case, right? So you've got to think about it in terms of this is now about dealing with global companies, with global needs, and over the next 10 years, we're going to see a CAPEX to OPEX shift. We will finish out our IT careers witnessing the change of a CAPEX to OPEX world, right? And it's going to be driven by a set of adoptions that we hopefully get to be part of. So I wanted to frame how we've been thinking about it. Spend a few quick minutes with it, and this is sort of our, you know, what are we doing in the community and how are we doing? So we picked up the flag with open stack last June. So 15 months later, we've been fairly active, we're learning a lot, and HP's had a fairly proud tradition dealing with open source. One thing I want to point out here is over the last six, seven months, we've gotten very active. We're going to be putting out some news around Folsom and our work there soon, so stay tuned for that. But I just want to point out, make sure everyone's clear, we are very aggressive and I think progressive for a company of our size in terms of being involved with open stack. There's, you know, despite sort of a lot of talk, we are actually actively promoting and getting lots of sort of contribution back into the community. And I challenge anyone to actually go look up the facts. Looking up facts tends to be trendy right about now, but this one really matters, and it's again transparency, it's transparency. So please go check it out and I'd invite you all to actually go look at it, it sort of speaks for itself. We've been very active, again, it goes back to the points of what I think is all about production workloads and our work here sort of really reflects that point of view. We've been particularly involved with getting open stack, as I'd say, at an enterprise grade credibility point of view and I've been able to work with the foundation and being able to set it up. Again, I think kudos to the entire folks, just not just sort of the foundation people, but all of the companies and all of the individual folks involved with it. I think it's critical that we have governance and transparency go hand in hand and it's great to see sort of the iterative process of it. So we've been pretty active there. We continue to sort of do a lot of work at the sort of nuts and bolts level with the community. We're doing a lot of work for example with the CI and the whole sort of deployment process of it. We've got fair amount of work there. A big part of our effort here for the next chapter is around this idea of bundling SLAs and orchestration and making it real. And for HP OpenStack is a key part of that. It's not just about sort of a compute or a storage infrastructure view, it's about a complete stack. And HP OpenStack, it's not just about OpenStack, we've been involved with open source for a while. All of these projects are actively part of the HP cloud. They're an active ingredient of it. So it's not just about HP IP, but it's about actually tying these things together and creating a more compelling iterative view and getting it to be in an enterprise great experience is what we're after. And one of the examples here, we've been very active with the notion of deployment and automation and how do you drive automation. I tell people about the HP experience on operating cloud services at scale for a company of our size that's been typically a hardware infrastructure player, running operating web services at scale and learning that experience is completely new, has been new. It's quite a learning curve, a steep learning curve. But one thing we've sort of figured out and sort of I think are investing a lot of time in is the whole idea around sort of the deployment and automation life cycle and how do we get better at that. So I'm gonna close with just a couple of quick points. The converge cloud strategy for HP really speaks to what we talked about. So last spring, this past spring we announced this as core strategy, it's really a framework. HP sort of coined the term converge infrastructure and what it really was a few years ago was the basic hypothesis that said tie server storage networking together, make it sort of next generation data center with a common backplane and deliver that. Well, since we did that, most of the industry is sort of taken to that. Converge infrastructure is now sort of a default view. So at one level beyond all the marketing hype, converge cloud is basically a similar design point. It's the view that says hybrid delivery of clouds are going to sort of center around two, three core models. How do you deliver private, public and managed clouds? The business models around them are gonna be different but some core things have to be common. This notion of a common platform of a shared level of SLAs, a shared level of architecture that can reinforce the notion of orchestration, management, security, provisioning is vital. So really converge cloud is really an HP term. It's an umbrella strategy. What we've also done, I've been at HP about a year and a half and in that time we've actually consolidated all of the different various cloud efforts under one umbrella converge cloud business. So we've taken all of our R&D and pulled it together. We've now sort of got a common look and feel and the idea is we wanna essentially build this around four architectural elements and the open stack element is the core piece at the foundation level. So our notion of converge infrastructure as a service really speaks to the idea of tying a common set of compute, storage, networking, infrastructure bindings and hardening that as a curation or a distribution of everything we do is make it a fundamental piece of sort of HP hardware and make it referenceable, make it sort of credible from day one. And then on top of that, build out a management secure layer. On top of that, build out an analytics and a structured unstructured point of view and then finally wrapper it with a common look and feel not just the notion of sort of one UI but really a set of experiences that give customers across the world a common look and feel to accessing the HP clouds whether it's private, public or managed. So that's really what the converge cloud view is. So and what the team that's largely involved with OpenStack has been the public cloud team which is a good chunk of folks here and our public cloud team by the way is where we're hiring and for those of you interested please check out our booth. We've got lots of cool things we're working on. So let me share with you in a couple of minutes here what we're actually doing. So for HP cloud, our idea of the cloud is not just to deliver infrastructure, it's to deliver the full stack. So we're actually building out a complete platform stack and with by platform it's not just developer tools as in Paz, for enterprises you need IT ops tools as well. So there's a set of tooling and services we've got to build for developers, for IT ops folks with which they can build and deploy workloads. For HP our goal is very simple. Running as many production grade workloads with an SLA at as high a utilization as possible is our business model. So with that we've got to attract true production large scale anchor tenants anchor workloads SaaS and ISV companies for sure. We've got to give them a set of tools to be able to wrapper all that. In addition to those tools open up an ecosystem a pretty vibrant third party ecosystem that affords you a bunch of services. Now where we stand we're never gonna build out a whole bunch of our services as other players are trying to do, they're trying to do the complete stack. Our goal is to be completely open and interoperable and partner. HP's had a history, a very rich history of partnering and we think our focus on ecosystem will allow us to do that. Having said that in our platform we've built out services like database as a service. We're doing analytics as a service. We're doing a bunch of other pieces. So the idea is we're constantly trying to balance out the notion of what is it that we think will add value to developers and IT ops folks building out and managing workloads and how do we enhance the ecosystem by tying these pieces together. And then finally the hybrid interoperability piece is my commentary on hybrid delivery. So being able to orchestrate workloads across multiple environments up and down infrastructure and applications is vital and that's what sort of that piece is. And then we wrapper this all with the notion of a marketplace where our partners in the ecosystem and all the different services ultimately end up getting monetized. So the point is we're going after the enterprise production workload but we're building a complete stack for what we think is that that serves the needs of those workloads. So we're delivering this sort of innovative way to do that. Our work here sort of reinforces that every day but we're wrappering it with the notion of a true enterprise grade quality of service and SLA that has real teeth and working on orchestration. Those are kind of the things and ultimately with a default view that it's ultimately all open. If you look at some of the alternatives hypervisors are us or big big sort of integrated hardware software solutions out there you're essentially locking you in and we think that time has sort of come and gone and you can see some of the movements you can see some of the affinities around companies that a few years ago were completely in single stack mode and now we're actually vibrant partners in this community which is great. So speaking of ecosystem I've said this before we're only as good as our ecosystem. As a platform we are only as good as the vibrancy of this ecosystem. So in addition to building out core infrastructure and platform tools we're going to market with a bunch of these partners delivering solutions for customers at the enterprise level. So we've done a bunch of work in storage in management and platform as I talked about in DevTest the notion of taking DevTest all the way to production and honestly this speaks for itself. We've got some fantastic partners many of you who are here many of you know here with us and we're learning tremendous amounts here. We don't think you can innovate fast enough and deliver these solutions by yourself. So our goal is not to go try to you know do a better Panzura. I think we'll work with a company like Panzura. I think we'll work with someone like you know Feed Henry or you know some of the other tools out and services out here. So we're pretty excited about this. We've spent a lot of time learning and we're actually investing heavily in the ecosystem. This is our portfolio today. I just want to point out one thing. We stood up our public cloud in May middle of May and we actually turned on a GAID SLA backed service around object store and CDN within 60, 45, 60 days after that competing services. Other services have been in the market were in beta for months. So we're spending all of our time really trying to get this notion of a GA service with a SLA because that's the way we think enterprise production workloads are gonna get real on a cloud, on the cloud, right? And so this is a set of services we've built. As I said, with our partners and our portfolio we're rolling out a whole bunch more. So stay tuned for some good updates there but we're really sort of excited about sort of the next set of I think work that we'll be doing around sort of the current release. Finally, if you haven't I'd invite you to take a test drive. Please go check out HP Cloud and give it a shot. There's a three month free access. We've got a booth up here. I think Jonathan mentioned there's a party later on today so I'd love to sort of meet you and get to spend some time with you in person. But again, I just want to thank all of you and really the community for the effort here. What we're trying to figure out is how do you get to the production workload view? And we don't think it's something HP does alone. We're certainly going to push very hard for it where we think the landscape is. But I think it's really the responsibility of the community here for us to sort of make it real. So at the next summit, I'm hoping that we're going to get even more announces and a lot more use cases and a lot more actual, I think customers speaking and standing up and talking about how this is all getting real. So thank you for your time. I really appreciate it. Thanks for coming out and we look to see you later on today. Don't forget to join us for our party later on. Thanks very much. Thank you.