 Okay, thank you everyone for joining today. My name's Adrian Ma, I'm from Cloud Dynamics. Today I'm going to talk about how we have interpreted and interfaced into OpenStack and made it available for use for enterprises. First thing is a little bit of background on Cloud Dynamics. We are a Canadian technology innovator. What we build today is what we call Cloud DC. It is a zero touch modular high density data center and it's fully term key in the sense that it's delivered and designed for service providers. Our goal ultimately is really to drive business value and increase I guess profitability and reduce costs for our customer base. So Cloud DC comes three main segments. At the very first layer is EcoDC. EcoDC is our own creation. It is a physical data center envelope data center facility. We use free cooling technology and we've done research over at Ryerson University to improve the cooling capabilities. We can bring our PUE down to approximately 1.1 or below using that data center fabric and we can deploy as small as two racks for our service provider customers. In the center is our SIF Flare. The SIF Flare is essentially the cloud infrastructure fabric that's normal, standard hardware you would get off the shelf from Cisco, HP, Dell and Juniper, et cetera. And that's where the different stacks would sit as well. So OpenStack will sit in there, CloudStack sits there. We have versions that work with Microsoft as well as VMware. And what sits on top of all of that is what we call CDOS. CDOS is our I guess presentation layer. It also provides capability for us to integrate everything into a single unified fabric. So we bring capability from SDN into CDOS and we're one of the few companies today that can deliver SDN in this scenario where it's not only within the data center but between data centers. And this is very critical because we can actually build data centers that are very small and now we can distribute them across the city without consuming an additional data center footprint. By doing so, we also have the capability of moving workloads around and the IP space around with it. And that's very critical in CDOS. So again, just a very quick overview of the things that we interface with in CDOS. On the left side is our CIF hardware stack that we talked about. That's where all this industry standard hardware is coming from. We are looking to integrate OCP into our technology stack as well. And that will be coming very shortly. The various virtualization stacks. Today we started out, I guess a few years ago building on cloud stack. And the reason for that was because of the enterprise type capabilities. OpenStack has come a long way in the last little while. So we are here today announcing that we are integrated with OpenStack as well. And on the far right, you'll see public clouds. So we have capability to integrate and present all the public clouds under the same interface. And we'll go through that interface in a minute here. I talked a little bit about SDN. Really, the key factor is that we're working and contributing also into OpenContrail. And Contrail is a product that we selected to deliver SDN and to provide the engine for being able to move our IP spaces around. And that's quite critical in our model because the bottom line is we want to move the data closer to the people. We want the data centers closer to the people. So having the ability to move workloads around is quite critical. Another capability that's interesting that we created is really the ability to actually subdivide resources within a cloud and to create a hierarchical cloud structure. So you'll see in the demo to follow that we can actually subdivide into different departments. Each department can further subdivide into different application groups or user groups and we can provide a detailed billing on each of these layers. Role-based access control, again, this is a very critical feature in the enterprise world and it's around being able to deliver I guess user partitioning. So you don't want necessarily a billing user to be able to access and provision cloud infrastructure and vice versa. So having different user profiles and at different layers of the cloud is quite critical. So this is just a kickoff into the demo. I was going to do the demo live today but I was worried about the internet connectivity. So what I did was I made a recording last night. I'm just going to pull that back and I'll walk you guys through it here. So the screen here that you see is actually our login portal. We're just logging in to create some cloud. Now, at the very first login, what you'll see here is a dashboard. It tells you all the resources that are available to you within that level of the cloud and it tells you what's allocated and also if there's multiple sites within your cloud that will be displayed. Also, here you have different events that you can see in the last 100 events. So for security purposes, you'll want to know what's always happening in your cloud. And I think basically that's the cloud just to refer to the diagram there. We're going to switch over to a sub-cloud right now. So essentially there's two sub-clouds. I'm going to pick sub-cloud number two. And in sub-cloud number two, what you'll notice is it looks exactly the same as a top-level cloud. You can do everything you can do at the top level. The only thing different is the number of CRU or the resources that are available to you. So the number of sites and everything are the same and you'll still have access to the same servers. The first thing we do in a cloud architecture is to create a VPC. This is the equivalent of a VLAN and that's a partition within your data center to be able to house all your VMs. So there's a default VPC with the account but we can create a brand new one. Just click through here. So the VPC is relatively quick. Actually OpenStack we've noticed is much faster than CloudStack in creating things. So I've created OpenStack Summit as a VPC. We are now going into the next layer where we're going to create some security zones. With security zones we can create different VLANs, essentially our subnets within the VPC. Now when you create the first VPC there's a default subnet that's created and that can be one you keep or it can be one you delete and you can add a different one. We've simplified this and this is designed to be able to support enterprise customers who want a simplified experience. So we're going to create a subnet here as an example for it. And just to show you some subnet ranges that we can support. Okay we're going to move on to servers now. So to create a server, I think what we're going to do today is to create a web server. So we're going to the server tab and under servers I'm just going to hit create. Pick the site that I want the server running on and it'll take a few minutes, there we go. So now we get to select our templates, what type of OS you're running. Here we can actually pre-provision different platforms as well. So it's not only just OS level and we're going to select a medium size template. Give the server a name and I'm going to stick it inside the VPC that we just created. I'm just going to put it in the web zone for the security group and we'll open up the security rules for that shortly. What's unique about our capability is that we not only handle what OpenStack does natively but we actually add additional capabilities, things like perimeter firewalls, hardware firewalls, load balancers. And all of this is actually being orchestrated by the same interface that you see here. So the server takes a few minutes to spin up, I actually recorded this live last night. You'll notice the time in the corner there so it just takes a few seconds. And all this is actually the same amount of time you would have in real time. So I'll get you some details on the server, gives you an IP address, the size, the OS template that we used, et cetera. Okay. So next thing we're going to do is actually make this server available within our cloud infrastructure. We've designed the system to be extremely secure. Our standard architecture is designed to be PCI compliant. So there's multiple layers of firewalls and security. So first thing we have to do is enable it for internet access. So before you can do anything to go out and communicate out to the internet that has to be enabled. So now it's enabled. We have a yes in the subnet. And the next thing we're going to do is actually go into the server and map it to a cloud IP. A cloud IP is actually making it publicly available within our cloud infrastructure. So this is one step before making it available to the public internet. So it's another layer of security that happens here. Now you see in the top right, it says reboot. This is a requirement in OpenStack after the NAT has been created. So we're just going to reboot the server. And just a couple more steps and we'll have a live server on the internet. Now again, this is because all these different layers of security are designed because they're meant to be supporting and mimicking enterprise infrastructure. So the multiple layers of security, multiple zones for or tiers within our security zones. Those are all flexible things that can be created in our environment. So you'll see now there's a cloud IP that has been created. And the next thing we're going to go is go to the perimeter firewall. So this is where we assign a public IP and we start creating some rules on the, this is actually going out to a hardware firewall on the outside of the cloud stack. So we're just, I think this particular firewall is a Juniper SRX series firewall. So now we have a public IP and I believe the next thing we do is we're going to add some rules to make it available on the internet. It's a great rule. It automatically selects the VM that's running. If there were more VMs, you'd have a bigger list. And actually I called the SSH but I think I came back afterwards and changed it to web on port 80. So you can check off the check mark and you can rename it if you need to. Okay, so one more layer of security in terms of firewall that we have to go through is actually the security zone. We have to add port 80 into the security zone itself so that maps all the way through into our infrastructure on the back end firewall. So we put it into one of the default security groups called web and in there we're gonna add a rule for port 80. So that is essentially how we created a web server. We opened up two layers of firewalls and we essentially started it up live. So what you'll see going forward, happy to give you more demos at the booth. We're over at E37 and yeah, I'd love to talk to you some more about that. Okay, thank you everyone.