 First of all, thank you everybody for sticking around for the last session of the day and you're missing out on free beer from HP, I guess. So what I wanna do real quickly was just talk about cloud and our focus is on delivering an open stack distribution to enterprise customers. And so we're gonna go real quickly through some of the highlights of why we think enterprises care about this. And then Rick and Cameron are gonna walk through a demo of some things that we've added into the open stack distribution that we think it makes it easier to be consumed in the enterprise. So I was asked by my CEO at one point, why cloud computing is important? Why do enterprises care? I mean, okay, we understand why Amazon does it, we understand why Rackspace does it, but why would an enterprise care about it? So we came over these slides as kind of just a little dramatization of a conversation between a business executive, line of business, and the IT. Business executive says, we need faster rollout of services. I'm getting killed by competitions doing things, I'm having to respond to the market. That's gonna cost you a lot of money, right? I mean, this is kind of how the conversation goes. How much? I don't really know. I don't have the visibility of my infrastructure that I might need. Well, come on, there's gotta be unused capacity. I hear about this virtualization stuff, and it's freeing up capacity, so you must be able to take advantage of that. Yeah, but I don't really know where it is. I've got this pool of servers out there, I gotta go in and look at each one of them in inventory. Well, you know what? I'd even rather pay by usage. And the IT manager says, no, that's not gonna happen. I just can't run the business that way. So the whole idea is once you go and implement cloud computing, then the conversation changes a little bit. We need faster raw out of services. It's later today, okay? Not weeks, days, hours, you know, minutes. How much? $1.50 or $2.50 cents an hour. You know, I can tell you exactly how much it's gonna cost. Same as Amazon. What if I have to expand or shrink the user base? It's fine, you're now in control. I'm giving you more control over the infrastructure that you can take advantage of. And I love you. Yeah, it's still not gonna happen, right? So what's really happened is the contrast here is that the IT manager in the enterprise has become a cloud provider. And that's really the core focus that they're looking at. But there's a follow on problem. If you do that, how do you give control, but some control, but maintain some control, right? I mean, you still wanna make sure that your line of business is deploying compliant images, security patches are applied in an appropriate fashion. And just in general, you wanna make sure that the line of business has got, make it easy as possible for them to consume things, but at the same time, keep some control. We've talked about, obviously we're here about OpenStack. We've been participating in OpenStack for a couple of years now. We actually are a Platinum member of the foundation. Alan Clark, who's a SUSE employee, is the chairman of the OpenStack board. He's also a longtime experience in the Linux foundation, the OpenSusa foundation. So he's a great experience in helping drive community, community development, community projects. We focused a lot on technical contributions around hardening, securing, improving Zen support. We've promoted OpenStack in the OpenSusa community. So all of our development now is done in what we call the OBS OpenBuild service so that our community members can more easily consume OpenStack as they test it out. But we're also delivering an OpenStack distribution. So this is kind of our 2.0 product that we're gonna start working on and Rick is gonna walk through some more discussions around that. All right, looks like we're scrunched up a little bit right there. So, well, SUSE Cloud 2.0, so we released our first version of SUSE Cloud back in August of last year around LinuxCon. And we are looking at doing our SUSE Cloud 2.0 in roughly the Septemberish timeframe. And there's some interesting things that we're looking to be able to include in that 2.0. And you can see we've got the color separation, the separating things out right here. And the colors actually indicate a few things. First off, the orange right here indicates the pieces that are part of the general OpenStack distribution. That's the part that's coming from the community that everybody's been doing a great job and we've been learning a whole lot about it. But there's more to it typically than just the OpenStack community code. There's a lot of moving parts that come into any kind of OpenStack implementation. We believe that we have a few enhancements and decisions that we have made to try to reduce the number of choices that you have to make as a customer to make things a little bit simpler. As we like pointing out, there's almost 800 different configuration options that you can choose in OpenStack. There's a lot of complexity. You can get paralysis by analysis. Some of the decisions that we've made, for example, is that we've partnered, we've taken advantage of the Crowbar open source project which was originally sponsored by Dell. And we are looking at establishing partnerships actually with, we announced yesterday, partnership with Dell to be able to offer a go-to-market solution of Dell hardware with Suiza Cloud to provide an enterprise-class cloud environment. Along with the Crowbar server and the services that come with it, we've made a choice to go with the RabbitMQ, messaging queue. We made the decision to go with Postgreffs as our back-end database to be able to handle all of the transactions back there. Then we have a couple of Suiza products that we feel complement these particular technologies and help you to get the most use out of them. The underlying one, of course, is our Suiza Linux Enterprise server which is the base product that we offer. The idea being that you can have an enterprise-class operating system that has all the testing, has all the security penetration testing, has all the auditing, has all the hardware certification, software certifications, all the things that keep you from getting fired for making a bad decision on your platform. Suiza Linux Enterprise server serves as the basis right there. We ship within Suiza Linux Enterprise server the Xen and KVM hypervisors, and as such, we support both of those as part of the open-stack offering. We are looking to expand those options in our Cloud 2.0. We are optimistic that we'll be able to get hyper-V support in there. We would like to get VMware support in there if the code is up to snuff and it looks like it's a supportable configuration. We'll have to see how things progress on that particular front. Some other products we're actually gonna talk about a little bit today. Up in the very top here, we have a Suiza Manager. Suiza Manager is a tool that you can use to be able to actually manage all of your RPM-based Linux distributions from a single pane of glass, whether they are your private cloud guests, any public cloud guests you have, your cloud infrastructure, your local infrastructure that's not part of a cloud, it gives you that single window into all of it and lets you have a hybrid environment that you can manage in one place. The other piece up here that we're gonna also show you today is one called Suiza Studio. A lot of talk has been made about going... It's your laptop. It's not my laptop. I don't know the password. Oh, okay. All right. A lot of talk has been made about getting OpenStack up and running and all the bits and pieces you need to get that done. But there's also another key point is that you don't just turn on the cloud just for the sake of the cloud, you want to actually run something on top of that. And typically the process of creating these images that you're going to run is a fairly cumbersome process and Suiza Studio helps you to really streamline that process and make it a lot easier for you. And then there are partner products. So we maintain all the OpenStack APIs. We don't change any of them, anything like that. So any kind of partner that... Any kind of third-party product that integrates with OpenStack will be able to integrate with Suiza Cloud as well. And we have a couple of them that we've worked with around billing and portals and governance and these kind of things. So we've got a number of partners that we're talking about. We already talked, obviously, about Dell. We have ones like Cloud Cruisers and Stratus and a couple other ones that are out there. There are several of them out there. All right, let's go ahead and move on. Okay, is there a question? So the question is, do we use MySQL at all for the database? The answer is no. We use Postgres. The engineering team is right there. They can answer that question for you if you want. Who wants to be with Oracle? That's the big one that I always tell people is nobody wants to be beholden to Oracle any more than they absolutely have to. Postgres has some really nice features in terms of HA that make it a really good scalable database. There are some other features that you can make the argument that Postgres is a little bit more enterprise-ready than MySQL is. Not to say that MySQL is bad, it's a great database. Okay, yep, good question. Thank you for bringing that up. Okay, so I'm gonna have to move a lot faster right here, but this is just kind of a quick overflow of how we see the overall lifecycle of a cloud deployment going. So basically you can have developers who are creating code applications. They're getting to check their code in. Pete already mentioned we have the OpenBuild service, which is a tool that we sponsor where you can compile code for any major Linux distribution and all the most popular hardware platforms all from a central place simultaneously. And from those custom packages that you can be creating, you can run those out into SUSE Studio or into SUSE Manager and then be able to use those to create the workloads that you need to be able to use on your cloud. All right, so we've mentioned SUSE Studio a little bit. I'm not gonna go into too much more of it simply because we're going to actually see the demo and you're gonna actually see us do some demo without a net. We did not learn from HubSpot. We're gonna try and do live demo here today. So let's go ahead and do some showtime. And I will increase the font size, I promise. Okay, where's your studio instance cam? Oh, that visible in the back there? I'll take that as a yes. All right, so SUSE Studio is a web-based tool. We do have a version of this that's up online at susastudio.com. That is kind of our community version where we sandbox things, we try out new ideas. It's not necessarily something I would want to base any kind of production environment on, but it does give you a great opportunity to be able to kick the tires and see if it's something that will work for you before you invest in SUSE Studio on site for your data center. All right, so let's go ahead and let's go ahead and create ourselves a new custom appliance to be able to do something. We're gonna start off, we have a number of different templates you can start from. This one is called Juice, just enough operating system. It's literally just barely enough OS to be able to boot your system, and that's it. So in and of itself, it's not terribly useful, but what it does is it gives you the ability to then take that bare bones and layer on only the pieces that you need to be able to accomplish your task. This makes your file size much smaller when you're dealing with your image. It also means that from a security and auto perspective, you have less exposure and risk because you don't have to worry about a specific service being turned off on the system if it's never on the system to begin with. All right, so let's do the 64 bit. All right, you sir out here in the front that was asking the question, what's your name? Prakasha? Oh, let's see if I can do this like that. We're not gonna go there. What does it say, Prakashas? No, it's a man instead of an H. I gotcha. Wonderful server. All right, so Prakashas wants to make a wonderful server. In this case, we're gonna do something simple. We're just gonna make a simple web server that we can come out here and just so you can get exposure to the ideas. Let's go ahead and let's see if we can find a way to. All right, we can see most of what we need to see right here. Okay, all right, so we can come in here. We can see the name. Let's go ahead and come into our software. We have a number of different ways you can add in software. You can add in if you have your own custom repositories, whether that's with the open build service or some other method, you can add them in right here. You can upload single RPMs. You can simply do a plain text search for whatever it is you want. We also have what are called patterns. A pattern is a pre-built configuration, a compilation of one or more packages that fulfills a specific role. So in this case, we're gonna do ourselves a lamp stack. Actually, we'll search in here. A lamp, we're gonna build ourselves a lamp server, just a simple Linux Apache MySQL PHP. We can look in here and we can see a plain text description. We can also see that by default, it's just the Apache web server, but we have these other additional recommended software we can add as well. Right now, we're just gonna do the basic one and add it in and we're gonna have ourselves in the Apache web server. We're super complex here. All right, so let's go ahead and configure it up. So we can go ahead and set things. We can set our time zone. We can enable our firewall if we have it, do the network if you're gonna use local authentication. You can set up your users and passwords right here. This one is surprisingly popular. Lots of people like to be able to customize. So you can select a logo. So if you have your company logo, you can upload it and put it in there. If you're really adventurous, you can get your webcam and take a picture of yourself and upload it so everybody has to see your face when they boot up their servers. Make sure it's a good hair day before you do that. I'll leave it up to you as to what your definition of a good hair day is. On the server side right here, if we had set this up to say a Postgres or a MySQL database, you can actually upload the MySQL dump file and set up your users so your database can be pre-populated and ready to use as soon as you launch your workload. I don't want to show this off the screen. Let's see if we can get to it. No, can't get to it. Well, okay. There's another button over here where you can actually click on the scripting and be able to see where you can do scripts that can be run at the end of the build or whenever the appliance boots, whether that's the first boot or every boot. So you have a lot of flexibility in terms of how you can configure up your system. You also have the ability to upload overlay files. So if you have a tarball-based application or if you have specific config files for say, authenticating to your active directory infrastructure or any of these kind of things, you can upload these configuration files and make those be part of your appliance. And then when we get to the build section, this is actually the kind of fun part, where you can see, you can build this for pretty much every platform under the sun. In this case, we're going to be doing cloud stuff. So we're going to select the SUSE of cloud slash open stack slash KPM and go ahead and kick off our build. And this is going to build us a QCOW2 image. You can see that we have a lot of other different options. Now in the interest of time, we're not going to wait the five minutes for that to build. We're actually going to go over and look at another one that we've already built while we're waiting for that one to finish off. So let's come over here and show you the next neat little thing right here. So we've got our appliance we've already built over here. You can see we've got a feature over here called test drive. What test drive does is it'll actually launch up a copy of this image on your system so that you can then log into it. You can activate networking and SSHM and copy in large quantities of files. And it'll keep track of all the file system changes that are made during your session. And then you can go in and grab those changes and pull them back and make them be part of your overall appliance. And this way you can, and then this way you can, you can be very granular and very detailed in terms of how you configure up your system. You get a lot of control. We're booting up over there. Okay, so while that is booting, let's come back over here and see if we're how we're doing on our build. In just a moment here, I'm gonna turn it over to Cameron who's gonna walk us through the actual cloud portion and seeing how this image that we have is going to be consumed on the cloud. Got a spinner. Everybody cross your fingers. Demo without a net. This is a lot of stuff to be running on one laptop, so. It's taxing that CPU on there. Yeah, we're picking it up. All right, I'm gonna go ahead and turn it over to Cameron while this is building. And he's gonna walk you through the actual cloud portion. Live demo. Gotta love it. So, we're gonna start out with a couple of things here. You're all familiar with OpenStack, of course. And so let's go ahead and open up the SUSE Cloud dashboard here and see how we SUSE-fied this little dashboard. Pretty common dashboard that you've all seen. In here, we have some images that have been loaded in there. As you've seen from Studio, this is actually one of the images that was dropped in there in a little bit. As this is building out. Actually, I'm gonna bring this down and see if I can't get this thing to fit on the screen just a little bit better. SUSE Cloud is getting hammered right now. Her studio is getting hammered. As you can see, that CPU is just chugging. This will probably help if we shut down Test Drive. So, you can imagine this whole, as we're talking about this SUSE Studio stuff and we're creating images and building your image so that it can be plugged into a cloud environment, namely OpenStack in this case. Think about this whole life cycle of these tools working together with the cloud. Building your image, having that image with everything that you want on it, your application and whatnot, and having that image automatically deployed right into your cloud environment. And that's exactly what we're doing here. Eventually, it will actually show up right under the images within this dashboard here. I've created a user in here. His name is www.joe. Now, there's a couple of things I've done with Joe, web user, and if we go ahead and log out of admin and log in as web Joe here. Can you increase the font size again? Sure, yeah. We're gonna log in as admin and reset as password. Okay, we're logged in as Joe. He's a tenant on the web team and he's going to start up an instance that we've actually created in our studio environment. And so we're gonna take a look at the images that are available. We have one that's Slesi 11 SP2. Soon we'll have one that is an entire LAMP stack that might be better for Joe web user. And we'll go ahead and launch this particular instance in the cloud. And we're gonna name this summit 2013. We're gonna launch that in the cloud. So it's starting up, spawning the KVM in the background, finding a compute node that's suitable for the size. It's, of course, a tiny one. And he's gonna start booting up. And during this boot up process, there's a couple of things we dropped into this image. This particular image contains information such as the necessary functionalities to plug right into SUSE manager. So when it boots up for the first time, he's gonna automatically register himself to the SUSE manager's management framework. So now we've created an image using SUSE Studio. And now we're plugging it in to our management framework as well after we start that instance in the cloud. So now we can do several things with that. This takes just a minute to actually boot up. Let's see where he's at. He hasn't quite got any networking yet. Any questions at this point? So he's asking what kind of control do we have over the images that we're putting up into this cloud environment? Is that right? So the control is with Mr. Joe user here. Whoever you're designating on your team to take care of those instances in your cloud environment. That's who's got that control. And you can go in there, you can stop those instances, terminate them at any given time. I think his question was on the images. So if you're building multiple images, how do you clean those up and how do you control where those go? Yeah, so that's a really good question. So on the images, when SUSE Studio builds an image, we have what's called a webhook on one of the control node that basically plugs in with Glance. And it's continuously listening for information from the Studio server. And when it gets information that it's got a KVM build that's ready to go, it will go out and grab it. If it's any other kind of build, it won't touch it, it'll just leave it alone. So it goes out and grabs that and then uses the Glance commands to import that into your cloud environment. So you can actually go in to the OpenStack web UI and go in and remove those out if you need to at any time. So you might see multiple versions in there. If you're building a new version of it, you'll see a new version in there if you've created an extra version. So you can also modify the listening scripts. For example, with the versioning scheme, you can set it so the only point releases, don't get automatically pulled in. You can have a logic such that only a .o release gets pulled into your cloud. It's very flexible in terms of what logic makes sense for you and your particular organization. Say that again? Upload, yes, absolutely, absolutely. If you ground them that within Keystone. Right, that's a good point that you bring up because SUSE Studio isn't just for our SUSE framework. If you have a framework that's already KVM-based, OpenStack-based, you could plug SUSE Studio into that. There's a question in the back? Is that Doug? Oh, two minutes. So Summit 13, the instance is already booted up here. And so he should have registered himself with SUSE Manager. Let's go over here and see what's going on with that. Go ahead and log in to SUSE Manager. Oh, that's the wrong link, sorry. And let's see what systems we've got available in here. We've got some cloud VMs and we've got Summit 13. He's got himself registered to SUSE Manager. And so this whole life cycle comes into play now. We have built an image. We have configured that image to be plugged into SUSE Manager. And now we've put that image into the cloud and he's booted up. And now you can see him being managed in SUSE Manager. So we have these life cycle of tools working together with OpenStack to be able to give you that life cycle management. And let's see if our image is built yet. Over here in SUSE Studio. Studio. Studio is doing so well right now. Anyways, he's probably stuck building and building at this point. Yeah, he's pegged on the CPU. Once he's done building, that will eventually slide right into the OpenStack framework there and you'll see it as an image. So if you wanna stick around after we're done here, then you feel free to come up and we can show you and you can see it and finish off and show up. Okay, that's what we have for you today. Kent, do you wanna go ahead and do the drawing? Okay, we got a little card for everybody. Everybody got your... Everybody else? Who's gonna be our impartial observer to draw this? Who do you mean? Who do you mean? Who do you mean? Pretty much for coming.