 Are we good? Hi, thank you for being here. We're Avni.io, and we're here to present our software defined cloud story. We're going to break the session into two parts. One is this very brief presentation that I will conduct, and then it'll be followed by a demo of our software that Vibhu Pratap will do. Vibhu is our VP of engineering. I run sales. So with that, I'll start. So what does Avni do? We're in the business of helping our customers, enterprises, service providers accelerate their journey into the cloud. We don't care what kind of cloud it is. It could be a private cloud. It could be a public cloud. It could be a hybrid cloud. What we do with our software defined cloud is to give you an easy button to deploy your applications unchanged as is into any cloud of your choice. The objective is to make sure that you have get the best speed for your applications, the best scale, as well as the best economics. And while we're doing that, we deliver cloud-like characteristics like self-adapt to scale and optimization. So imagine if you could just simply and easily run all of your applications. We really don't care what your application workload is as long as it is virtualized and it scales horizontally. We'll manage it for you. We'll deploy it. Use your choice of DevOps tool. Again, we do not put any restriction on what DevOps tools you may be using. Whether it is Chef, Puppet, Ansible, Salt, we support them all. And if something new comes out, we'll add that as well. And we also, of course, support your existing scripts. So we have the ability to take your scripts and include them as well. We already talked about the choice of cloud. So any cloud, any existing private cloud, whether it is VMware or OpenStack or System Center for Microsoft, support for Zen Server coming up, and any public cloud. So AWS, Azure, Google Compute, Rackspace, Century Link, Equinix, you name it, and we support it. And all of this we do by setting policy on your applications, which then get encapsulated into blueprints, which we will show you, so that your entire application stack gets deployed and is fully automated. So scales automatically, fully elastic, is able to support use cases for cloud bursting, cloud balancing, full performance assurance, service continuity, all through a single pane of glass for management. So how it works, we have a few software components. We have a controller, which we visualize or render as a studio. We have an analytics engine, which provides 3D analytics that we call raise. And then we include a test robot. So once you set your policy and you want to be, you want to test and validate that your policies are actually going to essentially run and comply with your requirements before you deploy your application in production, you can do that. So take an example of a three tier application. Here's a database tier, an application server tier, a web server tier. What we do is we frontend each of these application tiers with our service, a virtual ADC, or application delivery container. And that has all the smarts to then make sure that it scales either the application tier or the network services tier, the Layer 47 network services tier, based on what your SLAs are. So at the end of the day, what we're really providing is complete control for your application layout and behavior. You just need to set the policy once and it'll run in any cloud of your choice. We provide performance assurance and service continuity for your applications again specified as SLAs that the rib is going to show you are in the blueprints. So now you can deploy your application that are much lower cost, the kind of things that you expect a cloud will deliver to you and makes your applications, existing applications, extensible so that you're running them in clouds. And all this done through a very easy, simple to use graphical user interface that you will get a chance to see. With that, I will turn this over to Vibhu. Thanks, Rajat. Damn. I don't see it here. I just plugged into this one. No, he's setting it up. Yeah, use this output. Yeah, so this is the main dashboard for the product, right? As Rajat was mentioning, what we end up doing is we end up creating what we call application blueprints. So the application blueprint itself is for a multi-tiered application is, for example, for this particular application, there is a Python application which has security built in, the load balancing built in, what type of application you would like to launch, where you would like to launch those particular things, what are the SLA constraints under which that particular application is going to operate. So the software itself can be put on any hypervisor of your choice. You could put it on VMware, OpenStack, or Microsoft System Center. So all you need to do to deploy this particular application is just, so just one single click will deploy this particular multi-tiered application. What has gone inside that particular application is different profiles. So let's go into the details and look at what all is created in the profile. So this particular profile is where you actually specify where that particular application is going to be deployed. So the application itself, the same application, application bits and bytes, can be put on any cloud of your choice, right? Be it any public cloud or any private cloud. Once you figure out where you're going to deploy that particular application, you need to figure out what type of SLA constructs that you will have, right? What kind of a CPU metrics, memory, and so on and so forth that you want, what kind of SLA you would like to extract from the system. Then you would like to see what kind of a load balancing that you would want to create, right? So we have a load balancer, which is an only load balancer, which will be put in front of the application tier, right? But we also have integration with some other third parties like Citrix. So you might have an application which you want to do it in your Dev and test environment using Avni load balancer, but you would like to integrate with Citrix in the production environment. We have capabilities for all those things. So we have complete web application firewall built into the system, and of course then the application itself. So this basically talks about how you're going to deploy your application. We have integrated with Puppet, Chef, Salt, and Ansible, any of the configuration management tools that you might have in your system. So while this particular application comes up, this particular application is right now in the process of coming up. As you can see, once the application comes up, you can see the topology for that particular application. Oh, let the application come up. As we're waiting for the application to come up, one of the points that we want to make is all of our engineering effort has gone towards making sure that we deliver to our customers a vendor agnostic solution. When we talked a little bit about us being able to replace our network services with Citrix, the goal there is to be able to offer you all, any full choice, right? So if you're going to, hopefully in the future, want to use F5 or somebody else's ADC, we'll be able to substitute that, right? So you've seen that in terms of choice of clouds. You've seen that in terms of the DevOps tool. We will extend it to the network services as well. Yeah, so this in a nutshell, after you have brought up your application, you can do a bunch of tests on your application. What kind of, so if you see your application itself, you have a bunch of tests already built into the system, what kind of a security test, what kind of a load balancing test, and what kind of throughput tests you would like to put together on the system. So this will result in auto-scaleouts and other such things depending on the profile that you have picked up. So that in nutshell is what we have done. Thanks. Are you done? Yeah, I'm done. Anybody has any questions? We're happy to answer them. No questions. No? Well, thank you.