 All right, folks, let's get started. There we go. All right, so my name's Hernan Alvarez. I'm the Chief Product Officer for Bluebox and now Director of Offering Management for IBM Cloud. My scope is IBM Private Cloud. And now I'm roast recently, IBM Public Cloud based on OpenStack. So a few things to talk about in regards to all that. And then today, we're doing a session on modeling, deploying, and managing applications with Bluebox Cloud and Cloudsoft. My friend Duncan Watt is here from Cloudsoft. He's going to talk to you a bit about his platform. I'm going to talk to you a little bit about our platform and how the two work together and develop great applications. To get started, we're going to talk a little bit about some of the guiding principles that IBM Cloud uses. I'm going to focus on the top three, where it's really most relevant for us today, choice with consistency. And that's the idea of being able to choose your deployment mechanism, but making sure that you have a very consistent experience across that as a user. Whether you're buying public, local, or dedicated cloud, you should get the exact same service or the exact same experience across there as well as consistency in the services and industrializing hybrid cloud. So no matter how many of those clouds we're producing, whether they're public or local or dedicated, is that they're again extremely consistent. And one customer's experience is very similar to another customer's experience. And then within a customer, that's the same experience. So there's not a huge amount of drift inside of that. In fact, there's no drift with the product that we're developing. And ultimately DevOps productivity is where Duncan's going to talk about. But the idea here is the guiding principles at IBM and IBM Cloud is that DevOps productivity means business velocity. Giving the developers the tools that they need to be able to build relevant, interesting, and game-changing applications for any industry. The IBM Cloud Platform. So the one Cloud Platform is built upon this idea, this notion that you can deliver comprehensive services across the three main deployment mechanisms and consumption methods for a customer, whether it's public, dedicated, or local. What we're going to talk about today is Bluebox. And Bluebox focuses on dedicated and local infrastructure service. But that means that there's really high levels of consistency across not only in the entire, the three deployment mechanisms, but also that platform. There's also with IBM Cloud, BlueMix, who you're all familiar with and all the services that come along with that, software and solutions, and ultimately cognitive solutions from IBM Watson. So again, those products are meant to be delivered and consumed in the way that's most appropriate for the business. And so customers choose IBM Bluebox because of a high level of consistency and operational excellence within our tools. So we build, deploy, and maintain the Cloud for the customer. So we take care of the troubles of OpenStack. Now there's a lot of companies here inside at the summit today that are this week that like to and benefit from being OpenStack experts. And then there's a lot of customers that want to leverage the benefits of OpenStack, but not necessarily become experts themselves. And this is where Bluebox comes in. We build, deploy, and maintain Private Cloud as a service for the customer, meaning that they're always up to date and they're always patched and they're always secure. So the idea with Private Cloud is, of course, that it's a very high security environment. It's dedicated to that single customer. It's complete control. That customer has control over that environment. They can decide who comes in and when and how their neighbors come in and consume those services. And it's very predictable as a result of that. They know exactly who's consuming services inside. The Cloud, they're not dealing with the next Netflix coming in and consuming all their resources. So really, Bluebox is the best of public and private merged together. So it's a high level of elasticity with OPEX models and data sovereignty and cost predictability. So for those who've been around OpenStack for a while, you've probably understood that we are, remember that we got purchased by IBM back in June and it's been a very, very busy year. So we were acquired in June and then immediately we went into a product integration where we could deploy our products, which were, of course, based on OpenStack and delivered in our form and data centers across the world. But then ultimately into SoftLayer. SoftLayer has 34 data centers across the world and a lot more than our four. So we went into immediately to an integration expert there and got that rolled out to select SoftLayer data centers. And then in November, we built out our complete GA product and that GA product converged the best of what was happening inside of IBM OpenStack with the best of what was happening inside of Bluebox OpenStack. And then we also launched the Bluebox local product. So now we can take the operational excellence of Bluebox, which again is a curated, managed as a service OpenStack and then deliver that inside of the customer's four walls. Again, delivering on that overall cloud vision from IBM, which is the consumption method should be very easy for the customer and ultimately be very consistent across that. So we took the Bluebox dedicated code, moved it into local and based it on initially a Cisco appliance. And now we're working with Pure Team to be able to merge those together. So we'll have two hardware platforms coming out of this year that we can deploy inside of customer's data center. We grew the team significantly since the acquisition as well and then went into some really interesting and strategic installations with China. And then ultimately into Japan with some other customers where we deployed the very first Bluebox that was with Bluemix on top and Watson Cognitive Services on top. So within a really a few short number of months, we were purchased in June and in February we deployed the solution. We deployed a Bluebox managed cloud with Bluemix platform application and then cognitive solutions on top. So moving very, very quick, leveraging those really consistent APIs and really great engineering teams across the board. And then in March, we took those tools and we built a HIPAA ready solution. So again, taking those, the operational excellence of Bluemix in Bluemox and deploying a solution that can service very specific industries. Now, not just going after general purpose IS, but industries such as HIPAA that require a high level of operational control and reportability. Then we're going into the Bluemix beta coming out of March as well. So now Bluemix local is available on Bluemox local for any customer that chooses. So again, very high level of velocity inside of the organization. So talk about local and dedicated, give a little bit more clarity there. We start at the very bottom with any customer data center. So it's the customer's data center or a software data center. And we can deploy on either one of those consistently. Those can be consumed in either an OPEX or a CAPEX model depending on what's most appropriate for the customer. In software, when it's a dedicated service, it's OPEX only, but going into the local where you're actually installing inside the customer's four walls, it can be consumed as OPEX or CAPEX, whatever's most appropriate for the customer. Again, that's choice with consistency. And then on top of that is a local or dedicated product. And then really what ties it all together is the common operational model. So it's the same code. It's the same operations team. It's the same release procedures. It's the same remote management technology, same monitoring that really ties it all together that gives a consistent level of services. So whether you're buying it in a local or a dedicated context, you're getting the same experience. And that's really a game changer. So we started out with a series of data centers inside a software. We started with just a handful. Now we've gone to 16 or 17. By the end of the year, or by the end of the quarter, we'll actually be able to deploy every single one of them. And then ultimately we can deploy in any customer's data center across the world. We've already deployed the local product in three continents, multiple customer's data centers and high security environments. And we can continue to do that. So customers are gonna be able to benefit from Blue Box's experience in OpenStack and IBM's global reach in the world to be able to build compelling services. And then I'm really pleased to announce that we're extending the Blue Box benefits across the board. Most recently we've taken on the Blue Box, we've taken on the public OpenStack inside of the Blue Box team. And we're now leveraging the same tools and technology inside of the public OpenStack environment as we are in the dedicated and local OpenStack. So really high levels of consistency. And really people are gonna be able to build interesting apps on top of that. So what it is at the end really tied together is a proven OpenStack deployment with really strong community ties. IBM is a platinum member of the foundation. We've been in the foundation for three years and we feel that IBM or Blue Box are uniquely positioned in this way. So customers can gain an immense amount of value from hybrid cloud. We've seen people really need to be able to build and deploy applications based on the business's needs both in a dedicated and a local context. Very high security applications that need to be well contained inside of their four walls. But also being able to burst out into dedicated or even public instances where they need to, where they can put workloads that aren't nearly as sensitive. IBM is positioned to be able to uniquely deliver this. Not only with software, software's reach of 34 data centers and IBM's global capacity to build and deploy infrastructure inside of any customer in any country's environment. And really customers wanna work with OpenStack not on OpenStack. We're seeing this consistently across the board by leveraging IBM's platform. They can continue to do that. And right now it's available. Public, local, or dedicated offerings, IBM Cloud. There's a blue mix on top of that and a wide variety of other services. There's also Watson services on top. So customers can leverage the entire power of the IBM platform, not only from an IaaS, Paz, and Cognitive Solutions. And then Blue Box, as we talked about just a minute ago, Blue Box is now the foundation for all three of the deployment mechanisms. Public, local, and dedicated, and this is really exciting for us. So with that, I'm gonna pause and bring up Duncan. Got his mic on. I think I'm live. Yep, there you are. Thank you. Cheers. Yeah, thank you very much. So I think it's a bit late getting to the podium here because I was actually tweeting, apologies, but the key takeaway from Hanan's talk is the fact that the Blue Box expertise is now applied across the board. So when we first engaged with them, the focus was on what they could do for us around Blue Box, dedicated and local, in the case of customers. But the fact that they are now taking that expertise and rolling out the public cloud, the public open stack cloud on software is I think a massive, massive step forward. So I'm gonna switch gears and talk a little bit about CloudSoft, what we're doing and why we chose to run the CloudSoft application management platform on the Blue Box dedicated cloud. So start with a little bit of history. So we're always looking at the future, always trying to imagine what the future may be like and a lot of people here are involved in creating that future. But I like to also look back sometimes. And so if we look back to probably around 20 years or so ago, autonomic computing came into the limelight, really powered and enabled by IBM itself through what they call an EBO, an emerging business opportunity. And that theme of creating an emerging business opportunity around autonomic computing was probably a few years early, but if you now look at what's happening in the world of networking within Etsy and so on, you'll see the future of the autonomic, sorry, there is a thing called AFI, the autonomic future of the internet. So we've taken that same idea and applied autonomics to really the management of applications and services. So what does that mean? It means you model your application, so you create a blueprint for the application. That blueprint gives you all the essential ingredients you need to actually understand how to not just deploy an application on any underlying infrastructure, but also how to manage it on an ongoing basis. And that's really where the autonomics kicks in, because you don't just instantiate an application, then walk away, but you constantly monitor it. You sense its performance. You take sense data from it, and then you react to that and your effect will change its behavior. So that sends certain effect to pattern, and the monitor, analyze plan and execute autonomic control loop is at the heart of what we're doing. So our idea is to take that and apply it to any application so I can take the simplest application through to the most complex distributed system and apply the principles of autonomic computing to it. So we talk about being able to model, deploy and manage any application in any or in or on, I always hesitate whether in or on, I guess on any cloud. We'll stick with that for now. I'll probably change my mind halfway through this, by the way, but the idea there is to be agnostic. So it's being able to actually take this blueprint and capture the best practices around how to manage, deploy and manage the application before you decide to land it anywhere. Doesn't mean you necessarily start with a completely green field. You might actually leverage what has gone on in the configuration management space, using tools like Puppet, Chef, Ansible, Sort, and so on. But then it's taking that and then being able to constantly sense the environment. So this pattern of sense and effect comes through time and time again. So let's look at that in the context of the cloud. Well, the cloud is of course not the cloud. It's many, many different clouds. So these are just a sample of some of the clouds that we support. Now, when I say support, what I mean is we've leveraged other work by other people, in this case the Apache Software Foundation, to actually make this practical and make this possible. CloudSoft's own application management platform is itself built on another Apache project that we created a few years ago and contributed to the Apache Software Foundation where it graduated in November of last year. So last year was a big year for us because when a project graduates, it means a sufficient groundswell of people using it for it to actually make that sort of graduation step forward. So Apache, Brooklyn, J Clouds, all of these software, open source software components are packaged and bundled for you in order to actually deliver this cloud agnostic model, deploy, and manage. So that means taking this blueprint and running it in Bluebox, it's fine. We can run it on Bluebox dedicated local and obviously now we can run it on Bluebox Public although I'm not sure they'll be using the term Bluebox or the other thing we can do is work with more traditional clouds. So Software has its own API. There is an existing software, Public Cloud, 40 data centers around the world and growing. That number's probably wrong as I speak. So this ability to take the same blueprint and it is the same blueprint and deploy and manage it anywhere is critical to what we're doing. So let's look at a few use cases. So use cases vary enormously. I mean, if you were in the keynote yesterday, you'll have heard Donna Scott from Gartner talking about mode or IT, which is a Gartner concept around mode one, mode two and maybe there's something in the middle mode one plus. I was amused by some of the tweets that said, did somebody just kidnap us and take us to VMworld? I don't know if you've been to VMworld but it was a little bit of a strange moment there having an analyst kick off a conference like OpenStack having been to many of these. But anyway, I digress. So the first and most natural thing you want to do is take applications, take workloads and basically migrate those to the cloud. So there's two ways of doing that. There's the really, I'd say naive we're doing it where you lift and shift the application which I actually think of as more hit and hope. So you're really not actually adding value. You're just trying to scoop up what you have and hope to goodness that you can land it in a cloud somewhere. That really buys you know of none of the benefits of cloud. So the idea is to take a step back and actually understand, unpack that application, understand the components, the moving parts that make up that application and how they fit together, what the dependencies are and what are the best practices around how to manage those. Then of course there's being in the cloud using something like BlueMix or other cloud foundry based products be it from HP or Pivot or whomever where you have this very rich developer experience but you also want to be able to reach back into the enterprise and pull in data from the enterprise because you're not gonna copy an entire data set into your cloud foundry environment. I'm sure there are people who would try and do that but A, there are probably reasons not to from a governance and compliance point of view and secondly, it's a waste of time and effort. So the idea of being able to reach back into the enterprise to either stand up new services or to connect to existing services is a very important consideration. Then finally you can innovate, you can have fun. You can just go all in with cloud. So all three of those are valid depending on what you're trying to do. And I think that's a theme I picked up this year at this conference is it is a broad church if you will or a big tent, maybe that's a less religious connotation given you've got this election going on at the moment where we don't really want to talk about a broad church at all. Well, you may but in Texas but in general. I'm digging this really, really big hole here. I'm hoping I'll actually get out of the door let alone the state. So what do I mean when I talk about sort of modeling something and then being able to migrate it and capture those best practices? It means I can take this blueprint and guess what? I can actually deploy it to my existing infrastructure. So that same blueprint can be replayed and actually I can reuse that existing environment. Or of course I can go with a dedicated or a local version of a private cloud or I can go fully public. Pretty straightforward, I would have thought. Where it gets to be fun though is when you're looking at the integration with, I've said Bluemix here but as I said we've worked closely with a lot of the cloud foundry certified providers. These are all people whose cloud foundry based product is certified to be interoperable. So interoperability is another key theme that came out in, I don't know if you were at Dom Rippert's talk yesterday but he was talking about OpenStack as a community has done very well when it comes to innovation, integration, okay. But the interoperability is still a big thorn on everyone's side. So the cloud foundry foundation have addressed that head on and I would certainly encourage people to look at the, if you like the grand challenge that I've ever thrown out, the interop challenge which is sort of running as we speak. But the idea is whether it's Bluemix whether it's the helium development platform whether it's Pivotal cloud foundry or even cloud foundry itself. It's this idea of being able to actually reach back and then deploy services or access services again and these slides become repetitive by the way which is the whole point, yeah. So you're taking the same idea and now you're saying well actually I'd rather work with containers, fair enough. A container service is just a blueprint. Once you get it into your head that you're dealing with software this becomes, I wouldn't say trivial but it becomes much easier to think about. So from our point of view if I wanna roll out a private container service it's just a blueprint. The software happens to be Docker engines or Docker hosts or the software happens to be Apache Maysauce. But the idea is you take that blueprint you deploy it and voila, you get in this case form if that's what you really want. The fun thing is then having got that environment certainly from our point of view can I reuse all those blueprints I built previously? Even if it's in just a dev test environment rather than in a production environment so I wanna quickly spin up something that's a, you know, at least a proxy or an approximation to my production environment. We'll do it in containers, take that blueprint and by the way deploy it but this time it will deploy as a set of containers but the same logic that blueprint has now been applied across all of those environments consistently. So one of the things and it's only just occurring to me as I'm talking about this is choice with consistency is a message that you heard from Hanan. We take the same idea but do it at the application level which is probably why we get on apart from, you know, it's good to hang around with you but that notion of choice with consistency not locking people in is I think hugely important. So then why are we doing this with Blue Box? Well, I've kind of hinted I guess at some of this. We wanted, and I love that phrase, we wanted to work with open stack not on open stack. When we come to these conferences it's to be somebody who's a, I would hope a consumer or connoisseur of open stack versus somebody that's really in the weeds contributing to one of the sort of projects. Instead, we're guys driving, you know, how we see it should be shaped, what we need from it in terms of networking, compute storage and all those things but we want to be able to take it and work with it, not work on it. I'd already worked for a number of years before working with Blue Box on the software public cloud. So as a company we've been doing a lot of work with IBM over the past few years and so what intrigued me was this marriage between Blue Box and software and I've got a slide in a minute that talks about the 2.1 edition of Blue Box and what that's brought kind of together taking these two products but the key for us was could we leverage not just Blue Box but Blue Box running on software. Why? Because they have this second to none private network that ties all of the software data centers together. If you're not familiar with this, I'd say Google it, software three layer network or something or private network and you'll get all the goods. They thought about the network when they set out long before they were bought by IBM to build out this global footprint and I think that's really, really important. It was very far-sighted. I can see other companies starting to do that and so that was really one of the things that I saw as being immensely valuable. Rock solid support from Blue Box on the open side coupled with the benefits of the software under the covers. So just in terms of personal experience, our first data center, our first Blue Box cloud running in the San Jose data center was spun up very quickly in a set of two weeks. I mean, it came up very quickly. They then do this very good onboarding process where although it's there, they actually spend time with you. You get a customer success manager who looks after you and understands your requirements and that relationship becomes really important. By the way, be careful when you fire a support ticket with Blue Box because you'll get an instant response, not from one but probably two people. So if you check the box that says extremely urgent, you'll be inundated with people trying to help you. So we've used that mechanism for both the dialogue with the support team over things as we're fine tuning the environment as well as obviously if we have an issue we run into. But it's very important that that support is there. And now we've rolled out across three geographies. So as we talked a bit about this just before the break, I'll skip this in the interest of time but just in terms of why do we care about networking? Well, this is I think, you heard, if you like, the money shot from Hanan was what Blue Box are doing is now being rolled out not just globally within the dedicated and local but in the public OpenStack cloud IBM. For us, huge value was finally tying software and Blue Box together at the networking level. So we're really excited about this because it means that we can take blueprints that know how to exploit multiple locations and decide which workloads should run well, which parts of an application should run well based on any number of different reasons, be it governance and compliance, be it ensuring you have software rather than hardware redundancy. So having something like a React multi-location configuration so you can do replication across multiple sites. That's now enabled by the fact that there is a software private network that shows up in my OpenStack environment whether I'm in San Jose or whether I'm in London or whether I'm in Singapore, as a private internal OpenStack network. But the magic is that it shows up in all three of the locations. If I had a fourth, same thing will happen. So sort of cement that in your mind, this is what it looks like. So you saw that graphic. So that's probably out of date but that's essentially a sample of some of the Blue Box dedicated locations. So what we did was, as I say, started in San Jose, went to London, find. We've got two unconnected but still pretty useful Blue Box environments, Blue Box clouds, but with 2.1 they're now connected over this private backbone. So of course, once we saw that was working, what do we do? We fire up Singapore. Why? We want to actually create a fully meshed set of these Blue Box clouds around the globe and leverage that private network, which is hugely important that we see with many of the workloads that we're dealing with. So that's for us the key takeaway. So I'm gonna end with a call to action. So blah, blah, blah, blah, blah, act now. There is no planet B, okay? And so on that note, we'll close with a little vignette of what that might mean. 30 seconds and counting. Astronauts report it feels good, T-minus 25 seconds. 20 seconds and counting. T-minus 15 seconds, guidance is internal. 12, 11, 10, nine, ignition sequence starts. 6, 5, 4, 3, 2, 1, 0, all engine running. Lift off, we have a lift off. 32 minutes past the hour. Lift off on Apollo 11. Tower clear. See we got a rolling program here. We got an Armstrong reporting and they're rolling to get your program, which puts Apollo 11 on a proper heading. Just realized, by the way, I'm completely inept. You're still looking at blah, blah, blah. And I've just played you a video. Never worked with CEOs. It was fine on here. That, by the way, is the thing that kills me when a developer says, yeah, but it works on my laptop. Okay, so we just had a, yeah, but I could see it on my laptop. I do apologize. That's unbelievably inept. I will now blame Microsoft, by the way, because Oh my God. All right, so let me go back here. So, okay, so how'd I done that? Do we have time to play this one more time? I think we should, don't you? Sorry. All right. By the way, just so you know, that's what their knock looks like. So you never really ever get a glimpse of blue box's knock, but let me try again. Oh my God. You're not recording this, are you? Obviously the answer is yes. So. 30 seconds and counting. Astronauts report it feels good. T minus 25 seconds. 20 seconds and counting. T minus 15 seconds. Guidance is internal. 12, 11, 10, nine. Ignition sequence starts. Six, five, four, three, two, one, zero, all engine running. Lift off. We have a lift off. 32 minutes past the hour. Lift off on Apollo 11. Tower cleared. See we got a roll over here. The alarm's gone. Reporting in their roll and pitch program, which puts Apollo 11 on a proper heading. We got that in the end, so thank you for your patience on that. Obviously a very smooth transition there, as you have noted. So just going back and obviously now restarting the slideshow. Just wanted to sort of finish by play from the current slides. I'll spare you the entire presentation again. Just wanted to say that if you do go to cloudsoft.io forward slash blue box, then you'll see a tutorial that will let you walk through a real world example of what we've just described here, where you can basically spin up in this case a Maysauce cluster and then run the IBM day trader demo on that, which is used quite often in financial services as a kind of benchmark and is fun. So, because when you're doing all this stuff, whether it's the infrastructure or application management tier, demos are quite hard to come by, so that's worth taking a look at because it's a bit of fun and it's idiot proof. How do I know that? They use me in the company as the idiot to test these tutorials, and so if it passes the idiot test, then it's safe for you to use. So on that note, any questions for either Hanana and myself, and I've lost track of time at this point, but five minutes, great. Well, obviously planned to the last second, we have five minutes for questions. Or you get five minutes of your life back. And I just had to apologize on Twitter for letting you hang up there with the video not playing. That's quite right. Any questions? Okay, well, thank you very much for your time. Let's just leave you with, if I can get this thing to play nice. In, what, in about 10, 10 or 15 minutes time, we'll have Open Without Limits with Mark Shoderworth, who's a far more polished presenter, I assure you than I am, so I hope you can stay around for that and also for the rest of the afternoon. There's a great talk. I'm looking forward to myself on networking, which is linked to Project Curia. I think I've pronounced that right. I sat and stared at K-U-R-Y-R and I thought, yeah, of course it's Curia. It's obvious. Well, after a lot of staring at it, it was. And then finally, there's a kind of rappel and some traditional beers and whatnot at the end of the afternoon. So thank you very much. Thank you, Hernan. Thank you. Cheers.