 We're good. All right. Well, first of all, thank you, everyone. Quick show of hands. Who is already familiar with Citrix products in some way, shape, or form? Of course, these guys up front. This is my peanut gallery right here. So, OK, thank you very much. I appreciate that. Now, what I wanted to do is talk very briefly about the evolving role of IT today and how that really fits into both Citrix and OpenStack today. And we're going to highlight integrations into three of our products today. We're going to tell you exactly which projects we're integrating in and in what ways and show you some demonstrations as well. So first up, we're going to have Zen server. So I'm going to talk a little bit about Zen server, our hypervisor. And then we're actually going to do a demonstration of something we actually have new here called Zen server core, and we're going to introduce that. Next, Shridhar is going to take us through Net Scaler as well. So load balancing as a service with our Net Scalers and integration into Neutron, and also the Net Scaler Control Center software. And finally, I'm going to close it out with Cloud Portal Business Manager and what we call a connector and how Cloud Portal really allows us to do multiple workloads and multiple clouds in the background as well. Now, think about this for a second. Traditional IT, and I come from a data center background, data center operations for probably six, seven years at IBM, actually. And doing a lot of this over here, this very traditional workloads where building the servers, putting them in, getting the networking going, the storage, getting everything working. Very traditional applications as well. Well, what is going on is there's a need for Cloud in a lot of organizations. Could be private Cloud, could be public Cloud, or there's this kind of thing in the middle we're calling hybrid Cloud as well. So really, where do you go? It really honestly depends on the workloads, where what kind of workload you want is oftentimes the placement. Now, that doesn't necessarily mean you're building everything like you did in the old days. What we're really doing is evolving into where IT operations going forward is going to be both a provider as well as a broker to a lot of these services. And we're going to talk about that a little bit today. Now, how does Citrix and OpenStack fit together in a data center and providing these workloads? Well, if you look at the bottom of this, this is really your physical layer. So networking, compute, storage. Net scaler from Citrix is a physical hardware component. But at the same time, there's network services above it. So load balancing, firewalls, VPN, things like that. Net scaler covers this area as well. And then you, of course, have the virtualization layer, your hypervisor layer. Well, this is Citrix Zen server for here. And then OpenStack for the orchestration layer. And then lastly, on top of that, how do you provide these services and workloads out to the organization? Well, that is through a product called Cloud Portal Business Manager, which we're going to demonstrate at the end today. And this is really, again, providing workloads to all of the layers in your organization. Now, I just kind of threw this up here quickly. These are all of the projects currently that are official in OpenStack. And if I take those products that I mentioned earlier, first of all, Zen server hypervisor. And can everyone kind of read that from the back? Is that OK? I know the print's a little small. So Zen server hypervisor, plugging into Cinder, Nova, Swift, Glance, and Neutron. Net scaler load balancing as a service, plugs into Neutron. And then lastly, this Cloud Portal. Cloud Portal sits on top. And we're plugging into Horizon, Nova, Cinder, and Ciliometer today with Heat coming in the near future. Now, let's dig into each of those products in a little more depth. So a little bit about Zen server. So very mature hypervisor out in the market today. Over 1 million downloads of Zen server, the free version. Over 300,000 customers. And offered in over 50% of Fortune 500 organizations, empowering some of the world's largest public clouds. So it's been around for quite a while. And what's really nice about this is earlier this year, portions of it were always open source. Well, we actually took it and created what we call the Zen project. The Zen project was with the Lennox Foundation. The Lennox Foundation, what we actually did is we took a lot of the code and we offered it over to the Lennox Foundation so that it can be really organized and maintained going forward in a true open source way. Where it is a community led distribution. So a lot of the service providers are actually contributing back and helping us maintain Zen now. As well as a lot of very large organizations that are all listed up there. Now, what exactly do I mean by that? Well, before we open sourced it, there actually was other parts of Zen that were open. It's kind of weird, but it was open but not fully open, right? So what happens here is HA or high availability, the Zen center, the management, and the Windows PV drivers. This one in particular was where a lot of folks were wondering why we were kind of keeping those bits to ourselves. Because that is kind of a key integration point for a lot of organizations. Yes, sir. Oh, para-virtualization. And so up here, again, proprietary, we kind of kept this to ourselves. Well, when we did the announcement to the Lenox Foundation, we took all of those and made everything open source. So now Zen center is open source. The PV drivers are open source. The high availability is open source. But let's talk a little bit about behind the scenes what's going on here. If you notice, from this slide, the previous slide, to this slide, this packaging stayed exactly the same. The reason why that packaging stayed exactly the same is because we opened everything up, but we wanted to kind of get it out there. And we offered that Zen server ISO, that bootable CD, that installation experience. And we wanted to be able to continue to offer that to our customers. Now, what are we going to be doing going forward? Well, in the future, we're actually changing this distribution over here. Everything is still open and available. But what we're doing is we're actually changing everything to really offer the back end the way actually Zen server is built, is actually built with layers now so that it's not just one big blob like it was on the previous one. It's now packages based. And one of the great reasons to actually do that is because it allows the community, again, all of those sponsors that were in the Lenox Foundation or on that earlier slide. It allows them to more easily digest this, develop it, and contribute back, and keep the project very healthy. Now, when we do something like that, we get things like this. So we're going to do an introduction here of what we call Zen server core. So what is Zen server core? Think of it as a development snapshot. So we're taking the way we built everything in the background, and going forward, we can actually replace some of these underlying bits. You notice this isn't Zen server anymore. This is actually your Lenox distribution. So you can now load Zen server on top of Ubuntu. You can load Zen server on top of CentOS. So you can actually take an existing Lenox distribution, kind of do app get, Zen server, and turn a Lenox distribution into Zen server so that you can do the virtualization on top of it. Now, one thing, though, this is still kind of a development test kind of process. We wouldn't recommend this for production today. So with that, we actually have a demonstration of it. So Ewan's going to come up here. I'm going to flip to the video very quickly here. And what we're going to actually show you is a little bit of Zen server core actually working. I seem to flip. So hold on one second. Which video was it? Where's full screen? You going to do it? All right, you drive. Hi, so yes, I'm Ewan. I'm one of the engineers who's been working on Zen server core. And what I'm going to show you is basically how we anticipate Zen server core being useful to people. Zen server core is a dev snapshot of what we're currently working on in Zen server that you can easily deploy on a Lenox machine you already happen to have lying around. You don't have to dedicate a machine to it. And what we're going to see here is just a Zen server core, a dev snapshot running under dev stack, which is the dev snapshot of OpenStack. So to start with, what we have here is actually this Zen center, our Windows-based management application. And you can see we have two hypervisors. They're both marked as being Zen server core. And if we just have a look on those hypervisors, SSH to one of those, what you'll see is that this machine actually started off life as an Ubuntu 13.10. It was a completely standard Ubuntu installation. We added a pointer to our package. Yeah, it hasn't come out so well on this, but basically that's just catting, et cetera, release. You can also see that the message of the day said, this is Ubuntu 13.10. We installed Ubuntu from the CD, added a tiny bit of configuration to point it at our package repository. We then did app get install Zen server core, installed all these packages. There's a wizard at the end that sets things up. You reboot and you're running something which looks very much like Zen server. Zen center talks to it very happily. And as we'll see in a minute, OpenStack also talks to it in exactly the same way that it talks to Zen server, the ISO packaged product. So yeah, that's just the Ubuntu being highlighted. If we check out the other guy, it turns out that he started off life as a CentOS. So we have two different underlying base distributions, but when we layer the packages of Zen server core on top of them, they both look like Zen server from the point of view of the management tools. So that's just highlighting that. It's probably a bit easier to see. OK. So let's bring out, let's just expand that a little bit. So what you'll see now is that, as I said, we have DevStack installed on these hypervisors. There are two DevStack OS DOM U virtual machines. So on Zen, DevStack runs in its own virtual machine with all the tooling packaged there. One of the things that we're working on with Zen server core is the ability to move the DevStack stuff into DOM 0, which is the management domain. But in this demo, we had it in its own domain. As you also saw there before the window came in, there's another instance there, which is the DevStack managed instance, this demo instance. And slightly giving the game away, it was just a moment ago there in the state migrating. So what that VM is, it's just a completely standard Ubuntu. It's this instance 01 that you can see up at the top underneath the highlighted image. And it's migrating back and forth between those two machines, and it's streaming some video back. And this is just heading into the management DOM U. We'll see the command line just to show that VM. As you can see, again, it's migrating. There's just an input loop that's leaving it 10 seconds on one machine, and then moving it over to the other one. I'm going to skip ahead a little bit, if I can. Yeah. So what you'll see now is there's a video playing up in the top corner, which is telling you a little bit about the history of the Zen project, the open source hypervisor. And this instance, which is playing it back, is moving back and forward between those two hypervisors as it's playing the video without any drop of packets. And this is actually a live migration of the VM with block storage live migration as well. So there's no shared storage between these two hypervisors. When the VM is moved, the underlying disk image is copied from one hypervisor to the other, and then deltas are sent in the same way that memory migration does. And then finally, you flip over. So yeah, the key points to take away from this are both of these machines, these hypervisors, started out life as completely stock installations from their respective Isos. We installed the Zappi tool stack and the Zen server core packages on top of that. We got something which interoperates with anything that currently talks to Zen server, so both our own Windows-based tool and OpenStack. And then the final thing that we've seen there is the live migration between two different flavors of Linux. And that's that. Thank you. All right, thank you. All right, so let me just flip back here. Here we go. So again, the screen might have been a little hard to see. So I just want to highlight exactly what we demonstrated there. So we had two different underlying Linux distributions, both of them running Zen server core. Then we did a live migration from one to the other and back again. And then we want to point out that really at the end of the day, both OpenStack and Zen Center communicate using Zappi or the Zen API as well. So what does that mean to you? What kind of value does that bring to your organization? Well, again, Zen server today is our production quality hypervisor. Zen server core is really designed, again, development and test kind of environments get up and running. And then lastly, at the bottom here, we did core to core today. This ability to migrate bidirectionally between Zen server and Zen server core is something that will be coming in the future as well. And with that, I'm actually going to turn it over to Shridhar here to talk about Netscaler. So how many folks here are familiar with Netscaler? Or have they used them in the past? You've heard of them? OK, good. For those of you who are not familiar, Netscaler is a market leader in the application delivery controller market. What does it do? It does many things out of which the most salient features are really 100% availability of applications through world-class load balancing capabilities, high degree of performance through advanced features like caching and compression, offload capabilities such as SSL offload and TCP multiplexing to reduce the load on the back-end servers, and end-to-end security capabilities, including a industry leading web application firewall, and a industry leading access gateway function, and many other DDoS kind of protections. So that's the class of services that Netscaler offers. And how does it relate to a cloud environment? So if you look at what are the topmost criteria for a cloud provider, be it a service, be it a public cloud provider, or a private cloud provider, the first one is really how do I increase performance of my applications and services on demand as and when they need it? The second is how do I reduce the number of appliances and bring in simplicity through multi-tenancy and consolidation? Third is how do I expand capacity seamlessly on demand? And the fourth is as I deploy new services, how can I deploy them with agility and speed? Now let's look at how all these criteria are addressed by innovations within the Netscaler platform. So we'll talk a little bit about what we call the triscale technology. It's actually a core message which is built upon three dimensions of innovations driven through Netscaler. The first one in these three dimensions is actually a scale-up, is what we call that. It's actually a pay-grow capability built into each of our hardware platforms. It provides elasticity for unlocking new capacity on demand as and when there's the need for new capacity. We do that by applying new licenses on existing hardware so that you don't have to invest in new hardware footprint to unlock additional capacity. So it gives you investment protection. All our platforms actually support triscale and our mid-range, just to give you an example, our mid-range platform can scale up all the way from eight GBPS all the way up to 42 GBPS. That's like a five times increase just by unlocking additional capacity through licensing. The second one is really how do I gain simplicity through consolidation and multi-tenancy? What's most important there is as the application footprint in a data center actually increases, the number of applications, and the density of applications in a data center as it goes up, it's important for the provider to actually think about a sprawl in appliances which are often underutilized, and how do you reduce operational simplicity by consolidating your appliances and bringing in multi-tenancy into a single appliance? That's what the NetScaler STX is purpose-built for. It achieves simplicity by consolidating appliances without sacrificing performance or isolation, and we'll see how we do it. First thing that we did to achieve that goal was to actually make our appliance available as a virtual appliance. So our software appliance, which is called the NetScaler VPX, has the exact same binary and the exact same software footprint as our hardware appliance, which is the MPX. It's got the same build, it has the same features. It's available on AWS, it supports all the hypervisors, including Zen, Hyper-V, KVM, and VMware. So now we virtualize the appliance, but then what does the virtual appliance run on? Of course you have the option of running it on generic hardware, that's x86 running standard hypervisors, but we also have a purpose-built multi-tenant platform which is the SDX, which is purpose-built for guaranteeing performance without sacrificing isolation. So we've done many investments in different technologies to make this possible on the SDX. So it's got complete hardwalling of CPU, memory, and SSL capabilities, which are hardware resources that can be allocated to each instance. It's got complete independent entity spaces with their own networking stack and operating system for each individual instances. It's got complete independence in maintaining and versioning and things along those lines for administrative independence across different tenants within an organization. And in addition to being a platform to host net-scaler appliances, it also has been exposed, it's been opened up. The platform has been opened up to provide a home for third-party services, including security services and IPAM services and DNS services. And we work with some of the industry leaders like Paloalto Networks, WebSense, and BlueCat where they can run their virtual appliances on the SDX platform. And without sacrificing performance and isolation, you get the benefits of consolidation. So how does this all relate to SDN is something that we'll cover in a second. But I want to complete the third axis along triscale, which is around expandability. Expandability is all around how do I horizontally scale as and when I need more capacity for my ADC needs. So we accomplish that through our clustering technology. Essentially, you can take up to 32 different nodes of net scalers and manage them as one single entity. And it's a completely distributed architecture. All the state and persistence that you need, all the context that you need for your applications to run seamlessly, is shared within the cluster and the cluster appears as a single node to any external entity. And it provides complete N plus N redundancy because even if one half of your cluster actually breaks down, the other half can take up the load corresponding to the last half, basically. And our clustering is actually available on all our platforms, including the VPX, MPX, and STX. So in fact, you can take different instances on the STX platform, which is itself a multi-tenant platform, and achieve clustering not just across multiple instances on the STX, but across multiple STX devices. So you have clustering on two dimensions, basically. So this is pretty much the summary of triscale. And triscale actually lays the foundation for software-defined networking. And why is that? If you look at where today's conversations around SDN lie, they're mostly around dynamic procurement and provisioning of networks and network services. So network services that can actually scale up and scale in and scale out on demand from the underpinnings of a true software-defined services model, right? Now, what is Net Scalers' vision and what is Net Scalers' role in SDN environments? So as we look at sort of where SDN conversations are today, there are the applications. And then from a network standpoint, you have the programmable elements, which are today the physical switches and the virtual switches. And you have some sort of a centralized controller controlling these network elements programmatically. You have controllers from many different vendors. And today, a lot of the conversations are focused on providing connectivity at the underlying layer, so that tenants in the networks can actually procure connectivity, satisfy their connectivity needs through a self-service procurement model. That's what SDN has done today through paradigms such as network virtualization. And that's where things stand today. However, in the network, you also have a whole slew of network services, which we call the layer four through seven services, that include firewall services, IPS IDS services, IPAM services, visibility services, and of course, application delivery controller services. Now these services need centralized control also, where essentially you have an application control layer that can dynamically program provision all the network services in a seamless fashion and in turn can integrate with the orchestration engine so that you have a single pane of glass for all your layer four through seven services. If you think about it, so what does SDX give you? We just talked about SDX and what SDX gives you is a home that you can actually run your services on without sacrificing isolation and performance needs, right? But you also need a way to program and procure and lay down policies across all these services without having to worry about implementation details on what service should be installed where and what kind of policies should be applied on which devices. So the user needs to be able to express his policy needs in a very abstract fashion, right? And the application control layer is the one that's translating the policies expressed by the user into something that's more meaningful to implementation specifics around each of the service nodes basically. So and that's where we see ourselves as a net scaler, Citrix, we see ourselves playing a huge role there where we interact with the application. We understand the needs of the application as expressed in terms of policies. We program the network layer for communicating the networking needs of these services and then deliver sort of a truly orchestrated layer two through seven network. So that's Citrix's vision in SDN. Now, and what are the innovations we've done in that space? One is SDX as we already spoke about. That gives you a data plane element that is completely isolated and high performance, right? And it's been opened up for running multiple third party workloads. The other thing that you need to do there is really provide a seamless programming approach to actually programming policies in these services. That's where the net scaler control center comes into play. So net scaler control center is a single point of control for programming different network services on a wide variety of platforms. Today what it does is it applies net scaler ADC services across all the net scaler platforms including MPX, VPX, and SDX. And it has adapters that actually allow it to integrate into different orchestration platforms. So it forms a single pane of glass for visibility. It forms a single point of control for actually configuring services without being agnostic of which, without completely agnostic of which hardware resources are being consumed for the services the tenant is consuming basically. That's completely managed by the control center. It by itself is a, it's a multi-tenant management platform and it can be natively accessed to provide additional functionality that today some of the cloud providers may not provide. So what are we demonstrating today? We're demonstrating a way to enable load balancing as a service through control center and it's being deployed on the net scaler platforms which include both SDX and VPX. So we'll demonstrate two kinds of tenants. One is a bronze tenant and the other is a gold tenant. So the gold tenant gets an SDX instance just as a way for the administrator to differentiate classes of services between different tiers of tenants. And the bronze tenant gets an individual VPX instance which is running on a regular hypervisor. And the control center is the orchestrating instrument for provisioning these services on the appropriate instances. So we'll start with, we'll start with the administrator and illustrate the workflow of the administrator. The first thing that the administrator does is he'll add a set of devices to be managed by the control center. It's as though he's registering different kinds of platforms to control center as aggregate capacity to be managed by control center. In this case, we're showing you an example of an SDX device being added to the pool of devices to be managed by control center. That's the first step. So you see that all these fleet of products have been added but they've not been associated with any tenant yet. Now we're actually, now we go back to the tenant workflow and the tenant is actually logging in through the OpenStack Horizon dashboard. This is the OpenStack Horizon portal and he's about to consume load balancing as a service. So the first thing he would do is this is a standard, anybody who's familiar with load balancing would know the standard workflow for load balancing. The first thing he would do is to add a pool. A pool is just a representation for the set of servers to be managed by the load balancer. There's a name, there's a description. You associate a subnet which you would have created using sort of the Neutron APIs prior to coming to this workflow. So there's the subnet and then you select a protocol and then you select a load balancing method, standard round robin lease connections, things along those lines. So after the tenant has added the pool, the next step is to actually populate the members of the pool. What are the set of servers that you want to load balancing? Standard affair. And the members, the list of members that would actually show up are really the VMs that have been launched in that network. So there you go, he added pools then he associates weights with the members and specifies the protocol that's been added. And the last step now is really to finish the configuration is to frontend the pool of servers with the virtual IP. So that it's a single IP that is access to access a given service, right? There are additional functions such as session persistence that would allow a given client to always persist to the same server. That's also supported, it's not part of the demo. So that completes the configuration of the load balancer itself. And if you go back to the control center, you would actually, once the refresh screen is hit, you would actually see that now this particular NetScaler instance has been associated with the gold tenant on the fly by control center. So it's actually associating different instances with different tenants basically. Now we go to the SDX console just to see what kind of hardware resources have been allocated for that tenant. So if you see the instance, if you see there's a total memory, that's a hard allocation that's been set up by the provider. A certain number of SSL chips have been set up by the provider. The CPU has been set up as a shared CPU. And so that's the hardwalling that we spoke about for SDX. And the final thing is to actually see the load balancing work. So it's the virtual IP that's being accessed and they're being served from two different servers on the backend. Now, okay, now you've deployed the load balancer. What's left is really to see what are the operational characteristics of the load balancer that you just deployed. So NetScaler control center is a visibility tool also. So it'll let you see the status and the performance characteristics of the services deployed. So now it's the tenant logging into the control center and here's where he sees sort of performance characteristics and statistics for like packets and bytes transferred in the first byte, last byte, information along those lines for the service that was launched. So I'll stop the demo here. There is a second part of the demo which illustrates the same workflow, but in this case it's the bronze tenant who is using the service and he would be allocated a VPX instance running on standard hypervisor. So it's a multi-tenant deployment environment which is typical in a cloud environment basically and it supports different classes of services. Today what we showed is a basic load balancing service but we also support SSL termination as an advanced load balancing function and we're aggressively working towards a roadmap for advanced features such as layer seven inspection capabilities and content switching and advanced ADC functions including compression and caching basically. So that's the demo and I'll open it up for questions. The basic load balancing function is actually available in control center. It's also available in open stack. So we go, what we just demonstrated the load balancing as a service functions is actually exposed through the open stack Elbas APIs within the Neutron project. What are the questions here? Yeah? Yes, yes. And we can, we hook up the net scalers in an indirect fashion. It's actually orchestrated through the net scaler control center and we support all different platforms of net scaler today from day one which includes SDX, VPX and MPX. Actually it's both because the first thing we did was to actually build a VM so that there's a VM that can run, it's a net scaler VM that can run on all different kinds of hypervisors including Zen, like I said, all the hypervisors, right? Yeah, KVM too. And then now we also have purpose built multi-tenant platform that can actually run different VM instances of net scaler and can host them in an appliance. All right, we're gonna move on to the last one which is five portal business manager. So what exactly is this? So what we're seeing a lot from our customers is this concept of first of all, two kinds of customers. You're users that want to get services and then going back to that very first slide that I was talking about, that evolving role of IT, the actual cloud administrators. Now what we wanna be able to do is offer multiple services and multiple workloads through a centralized interface to the organization and really honestly front end multiple cloud services on the back side. So really doing things like self-service discovery, billing, charge back, show back kind of features and really taking your services, packaging them up and in a multi-tenant environment really showing the ones that you need to each tenant as needed. And then on the back end really could be public cloud, could be private cloud, could be a third-party Paz kind of configuration. We're doing a little bit of everything and anything and really offering many different services when it comes to cloud portal business manager. And what we've done here and again, you noticed on the first slide, I mentioned this is a tech preview. So this is available today, you can download it today but what we're doing is we're connecting to OpenStack and so we build connectors on the back end to all of the different cloud services and we have a cloud portal, or CPBM as we're shortening it down here, connector for OpenStack. The one we're looking at here, again being tech preview, we say experimental reference connector. Now what does that mean? Experimental means we're still working on it. We don't support it in production just yet. Reference meaning it being open source. And so what we're looking to do here is what will this do and what advantages do you get when we actually plug into OpenStack? Well, we get this self-service account and user creation and provisioning and it's kind of hard to see up here, I apologize but what we're actually able to do is create users from within cloud portal that will populate within OpenStack. We're able to offer service catalogs so we're able to bundle services together and then we're able to take those and everything in cloud portal is really done with what we call subscriptions. So you're offering subscriptions to your users. They can subscribe to virtual machines. They can subscribe to volume. So storage as a service kind of configurations and you can present them and then really kind of do some billing, charging, showing back kind of things depending on your organization if you want to do that. And then also we're integrating a single sign-on feature into OpenStack so we can directly interface the horizon UI from within cloud portal as well. And this is where if you're familiar with the OpenStack projects and what each of them do, Celiometer is actually that collecting of metrics. We're able to do that here and we actually collect on a good number of them. On the virtual machine, volume, image storage, network. We're able to really take all of those and give you a consolidated view, not just with OpenStack but across other platforms that you're using or other services that you're using as well to give you a consolidated dashboard view of how much your consumers are actually using in a given timeframe. Coming up next because again this is a tech preview. We want to do support for heat. We want to do full Keystone integration and obviously upgrade it for Havana. Right now it is still grizzly based. What I want to do here is flip over to a quick demo of this. This one is pretty short and I hope you'll be able to see it. Let me just fix this here real quick. Unfortunately this video gave me fits earlier so I'm hoping that it will play. Unfortunately it is not playing. All right, so let's do this. I'm gonna skip past this one because actually I'm short on time anyway. What I'd like to do though is tell you this full demo is actually running in our booth as well. So come by and take a look but at the end of the day what we're looking to do is not just solely talk to OpenStack but talk to multiple cloud services and really consolidate that viewpoint down. So why would we do something like that again? What's the value here? We're reducing the IT operations and we're providing almost like an app store like user interface and an enhanced user experience with single sign on and better visibility. This is really the key right now. Better visibility into not just what you're doing with OpenStack but maybe what you're doing with AWS, what you're doing with OpenStack, what you're doing with CloudStack, what you're doing with Citrix Cloud Platforms as well as many other vendors that are in the Cloud Platform ecosystem as well. So if you're familiar with platform as a service there's active state in there. There's a lot of other applications that we can actually plug in and monitor from this interface. And with that I've got a quick summary slide after this but what questions do you have about any of that that I just said? Or any questions about Zen server or any of the others? Yes sir, absolutely. Is that out of the box? I think it is, but good. So again, one of the key messages there is control center. So Net Scalar control center really being that central access point for everything Net Scalar and again aggregating all your services. Very similar to what we're trying to do with Cloud Portal as well. And so let's do a quick summary. So again, the way we see it is that evolving role of IT from just straight up operations to really operations and brokering as well. And we talked about Zen server, Zen server core and how that will plug into Nova as well as all of the other projects. We talked about Net Scalar's load balancing as a service and the integrations with Neutron and control center integrations. And lastly the Cloud Portal, the service consolidation and how we're able to really front end multiple cloud services with that product and consolidate all of your usage within an organization or a multi-tenant environment down. And with that, we'll take some questions. We'll be around for a while. I will upload these slides to the OpenStack Foundation site later today. They will be available tomorrow for you to download. And then as well, come by our booth. We've got many different demos running in our booth. We've actually got the Zen server core demonstration running. Running another one with Intel as well called Mystery Hill and you'll have to talk a little bit more about that and ask them about that. The Net Scalar demos are running as well. And then of course, I apologize. It didn't like the resolution of this video screen for some reason, but the Cloud Portal demonstration as well. And with that, I'll say thank you for your time and enjoy lunch.