 Thanks for coming to the session demonstration on course stack. It's orchestration simplified. Before getting into the demo, let me just introduce myself. I'm Venkatesh Perumal. VP Business Development with course stack. And here is my colleague, Ratha Sababhati. Call him Sabha. Yeah, I'm Sabha. I'm a CTO with course stack. Thanks, Sabha. So I'll just give you a quick preview of what we are going through today. So the very first one would be what is course stack is all about. What is course stack? And then what have we done differently in terms of course stack? So what is the incremental innovation? Thirdly, we will go through how course stack applies to all the IT stacks. How does it orchestrate across the layers of IT? Fourth would be our features. There are some cool features in the product which I'll go through in the product itself. And then fifth, we'll try to show you a couple of use cases, right? What can be solved as part of this particular product? And finally sixth, I'll go through the product itself with one use case and you'll be able to literally visualize as to how easily you can orchestrate using course stack. Well, course stack, it's a converged orchestration engine. It's a template-driven orchestration engine to configure, provision, deploy, and also it makes your IT operations task very, very simple. It spreads across your heterogeneous layer. When I say heterogeneous, it is an enterprise or a service provider who would probably have a bare metal as a service. He could probably have a virtualization environment, a cloud environment. That's precisely what I'm talking about heterogeneous. And it also has the capability to work along with various other tools that are part of the landscape. Well, what is so new about course stack, right? So it has mastered the template for simplicity. It basically means today if you look at OpenStack, right? You've got heat. Heat is a template-based orchestration, right? We've got Mistral, which is also template. We've got Murano, which is also template. In AWS, we have CFN. We have Tosca. So there are so many standard templates out there in the cloud area, right? So each has got its own specific DSL format. The beauty, of course, is it can understand any template format and it can execute. That's the best part. So even at the later point, if you have any new template format coming in, you should be able to use course stack and orchestrate. Secondly, extending capabilities for temporization. What basically it means is today heat has got certain capabilities. We have extended the capabilities of heat to orchestrate multiple clouds. Similarly, Mistral, we have extended capability to talk to Puppet, talk to Chef, and we can extend it as the product matures. Integrating relevant tools for the best business value. So in any ideal landscape, you'll have your own set of tools. We are not there to replace any tools. We are trying to coexist with them. We'll integrate it and use it for the best value. That's what it's all about. So when I was talking about various layers, so an enterprise or a service provider will eventually have a stack. The first stack will be your infrastructure stack. So you have a compute, there's a bare metal, or the bare metal you have virtualization layer, and then you have various cloud that an enterprise can adopt from a private cloud or from a hybrid cloud strategy perspective. Then comes your configuration tools. It could be Puppet, Chef, Ansible, and Solstack. On top of all these layers is what course stack sits upon. So what it does is it protects you from any IT changes that may happen in future. So tomorrow there's a new technology coming in. If your idea's landscape is changing, course stack will make sure there's a seamless integration. The course stack engine remains the same. We'll build in the plugins and ensure that there's no impact. And similarly, today if you're using specific configuration tool in your environment, we are not there to replace it, but we are there to utilize the best out of that particular configuration tool. Features, there are a couple of very good features where I'll go through the product itself. As I was talking about, it's template-driven. It's very, very simple. It's just a set of instruction or input parameters that an IT ops guy or an admin guy has to input, and your template starts running and it can provision, it can configure, do what it was supposed to do. There's another feature called template builder. The more and more DSL standards are coming in or DSL formats are coming in, what we have done is we've made it very easy for the IT team to basically do a drag and drop of resource elements and then create the template just by a click. Currently configuring workflow engine. So here what we have done is we have tried to integrate with the business process management of your enterprise or organization. So if you have a process, how that can be represented in a workflow, and then when you pick off the workflow, it starts executing the template based on any dependencies. Thirdly, triggers. Trigger, once you build a template, the template can also be triggered based on any event. So there are monitoring logs that are coming in and you know that you have to auto-scale. So a template, you can already define a template for auto-scaling and the moment you read the log and you say, yes, it has reached 80% of utilization, you can trigger the template automatically. Scheduling. This is used predominantly, this is used at the IT ops level. So you have to take a regular backup, regular snapshots, and I want to run a specific template on a specific day or a recurring format. So this particular feature enables you to schedule a specific template and it can execute. So if you want to take a snapshot on the first day of every month, you can just create a template, schedule it, and it takes care of it. Service catalog. What it means, right? So you're creating templates after templates after templates. Essentially what you're building, you're actually building a catalog for addressing specific use cases and which could be reused again and again by your team. That's the catalog and it's a repository basically. Bidirectional third-party integration. We are actually flexible enough to integrate with whatever IT tools that are there in the enterprise or service provider and we integrate that with our tool and you're able to have a single pane of glass in terms of orchestrating across the layers. Role-based access control. This is very much required when you are dealing with provisioning and configuration. So you have to segregate users who can only provision or who can only create a template or delete a template, right? So there's also a lot of control built into that. Multitenancy. So this comes into the picture when you have, you know, we have a lot of departments in an enterprise from a service provider's perspective. They have a lot of customers. So this is a multi-tenant application wherein you can onboard a customer, you can create him as a tenant, and then you can basically take care of the customer using that own entry. Notification alert. This is based on reading the logs of monitoring tools that are being set up. So let me just quickly go through the features. So I was talking about the use case. There are plenty of use cases today. What I'll walk through is the deployment of a distributed application. Usually what happens in a distributed application, right? So let's take a two-tier application. You need an app server. You need a DB server, right? So you want to provision two instances. You want to install an application, and then you have to configure an application. On top of that, if you want to monitor those applications, you can insert that script as well into one template with one click. You are able to deploy the application. That's exactly what it is. And from a use case perspective, it is not just limited to deploying distributed application, but also you can provisioned by a middle. You can configure your devices, which are basically switches and routers of any kind. You can install OpenStack itself with a single template. So there are numerous use cases. So let me just quickly get on to the product itself and show you how it is done. I'll walk through the features, and then I'll run a template. You can see how easy it is. So this is the dashboard, right? CoreStack dashboard. And on the right top corner, basically there's an admin features. If you look at service accounts, those are... If you click that, that actually provides you the kind of service that you have in your infrastructure, right? You could have a cloud. You could have a private cloud. You can also have a virtualized environment, and you could have a couple of bare metals. So you can create all those things as a service account. So in this case, you know, in cloud, you can add OpenStack. If you have OpenStack as a cloud, you can add OpenStack. If you have a hybrid cloud strategy and you are using AWS, you can add AWS as well. So basically you're trying to orchestrate across various platforms by adding them as a service accounts. Once it is added, so next one is resource elements. Resource elements is the place where you go and register your device, right? It could be a switch. It could be a router. Now, even for resources, you are... Costags gives you a flexibility of creating one template to provision, to configure the device. Then comes the user... Yeah, templates. So this is what we were talking about, right? So templates, what are these templates? So this particular list basically gives you a repository of all the templates that you build. And essentially, it becomes a guide for you and then you start using it. You can share it, and each and every template is categorized as it could be a global template. It could be a project or it could be a private template, right? And these templates are classified. You can classify those templates as, okay, this particular template is used for provisioning alone. This is for configuration. This is for backup or catalog builder. Right? So when I was saying that, we also coexist with other configuration tools that is done through the scripts. So if your organization uses a Chef or a Puppet, we basically import the scripts of Chef and you can use the script or provision the script directly out of CoreStack or you can also attach to a template. I'll show you when we run the template of a distributed application. Schedules. This is the part where I was saying that you can create a template for taking a volume back up every Monday and this is how it looks like, right? So you know there's a calendar. The user knows that, yes, I have a schedule which is scheduled to run on, you know, this Friday. So let me go have a look into it and you get a notification. When you try to schedule it, you get a notification that your schedule is kicked off. It has run successfully. Jobs. So when you execute a template, it basically submits as a job and once it submits as a job, you can actually look at it at a runtime. On the right side, it gives you the log of what are the steps that it is executing at each level. At the end, at the output, it basically gives you a link and other information for you to access the output. The other cool feature is the template below that I was talking about, right? So here, let's take an example that you want to provision instance. What would you require? You would require a network and you would also require a compute, right? So once we go to network, in network, you require private network. So you drag and drop. You require a subnet. You drop. You require port interface and port, you drop it or drag. You go to compute next, right? So in compute, what do you require? You require a key pair. You require security group. And then you say, create the VM. So this actually becomes, the moment you hit the build, which is on the top, it creates the template. So really, you really do not need to code a DSL. There's no template. You don't need to know any format. This particular feature takes care of it. It is not only limited to that. The moment in the compute, if you want to deploy, so for your use cases, provision an instance and deploy an application, there's a feature called deployment. You just take the application and drag and drop. Once it's provisioned, it goes and deploys the application itself, right? So it's a classic case of wherein it exists with, you have a DSL and also script is embedded into a single template. Workflow, this particular feature suits very well for service provider as well as for enterprise. A classic example would be now a department wants a private cloud, OpenStack private cloud to be installed. What would typically the process would be in an organization, right? So you will have a process called, okay, I want to go and gather requirements. So I go and gather requirements as to how many servers I require, what are the switches that I require. You basically get those specifications. You click the process, it initiates it, and each of the process where it says go ahead and install, perform network configuration, all those tasks at the back are actually associated with the template. So the template executes at the end once the process finishes, your OpenStack is ready, right? And at any point in time when you go and look at the execution, it basically tells you where the process is stuck, right? I have made the request. It's been, I've been waiting for two days. I really don't know. This particular tool will tell you, yes, okay, it's actually waiting at the install level. Now, let me show you how we can deploy a distributed two-tier application and then how it runs, right? So taking an example of SugarCRM, which is a two-tier application, we require a web server and a DB server. So the first task would be to launch a DB server. Second would be it will launch a web server. Then you will define the security groups. It will install the applications, and then you will configure it, right? So this particular template takes care of the entire steps one by one. Even execution has been made very, very simple. It is all parameter-driven. You say, what is the cloud service on which I need to run? I say HP Cloud. I want to run it in a U.S.-East region. You just enter the parameters, and then once you hit Run, you will see that it will get submitted as a job. There you go. So at every minute or two, if you want to go and check, it basically scrolls down, and you will see that it has run. Let me show you how it looks at from a horizon perspective, right? So you want to see what it is doing, what the job is doing. So if you go to the U.S.-East network topology, so the network is there, the VM has been created, and I'm sure the next steps will be following. The SugarCRM is there, the MySQL server has been created, and you can easily monitor it, right? So on the right side, you're now seeing that in which step it is currently running. If you go up. At the end, once the job completes, you get a link which says, you know, go ahead, access the application through a link, and you know that the application has been installed successfully. Okay. All right. Do you have any questions? Yes. I'm not able to hear you. We monitor both, actually. We can monitor just the infrastructure layer, the availability of the VM, or we can monitor the application availability, or we can also monitor the different parameters associated with the VM, like monitoring the CPU, or like, you know, monitoring the MySQL services, all that. Any other questions? Any other questions? Okay. If you want to know more about the product and also the demo, we are at the booth C19. We'll be happy to walk you through in detail. Thank you. Thank you very much. Thank you.