 Thank you. Hello, everybody. Welcome to a brief presentation on Anuta Network's nCloud X product. My name is Srini Biredi. I'm a co-founder and CTO of Anuta Networks. So what we have here at Anuta is a network controller. It takes the existing network and provides the network as a service, all the functionality that is required to make your network and offer it as a network as a service. So we have nCloud X supports multiple devices from various vendors like Cisco, Juniper, SweetRx, F5 load balancer, things like that. And also, we support multiple network topologies and various form factors also, like physical devices and virtual devices. Before I go deeper into the nCloud X product, let me talk about actually what are the challenges in creating the network services. Let's say you are a provider trying to onboard a network for a tenant or for an application. What you need to do is provision the network these services at various levels. You need to provision the access policies at your vantage. And also, you need to provision the layer three isolations, layer two isolations, and security policies, load balancer policies, things like that. Basically, it involves a lot of manual configuration. And it roughly takes about 200 or CLI or API commands. And also, usually, it's very manual, so it's very error-prone. What we are doing with the nCloud X product is automating the whole process. We give you a service designer to design the network services that you want to offer to your customers. And once those services are designed, they can be published into the catalog. And then when the customers are applications requesting those network services, we deploy them. We provision the network resources. And once the deployment is done, we manage those network services. So this is our nCloud X architecture. Basically, we have a network abstraction engine which abstracts the legacy physical devices, programmable network devices. And also, we can talk to STN controllers to use the virtual networking features that they provide. And the core of our product is the bunch of engines, actually, network service design engine, orchestration engine, and service management engine. All this functionality is exposed via the REST API so that this functionality can be integrated into the various cloud portals, such as Cloud Stack, Open Stack, and vCloud Director. In fact, we have an integration with the vCloud Director and Open Stack. So any Open Stack integration we actually show in our demo today. Let me go deeper into what we provide. We provide the entire lifecycle of the network services with starting with device discovery. So using the various protocols like SNMP, CDP, LLDP, we can discover the devices in the network, how they are connected with each other, and what are the capabilities of those devices. And then using that information, we construct the network topology. And once that is done, providers can design the network services they want to offer on their infrastructure. And we'll go more deeper into how we enable providers to design the network services. When the network services are designed and published into the catalog, they can be ordered or available to the cloud portals. And when they orchestrate or other services, we look at the actual infrastructure and map these logical network constructs into the resources and provisioning required on the network infrastructure. Provision these network services. And after that, we actually manage those network services to enable the troubleshooting. So this is our network service design engine. So what we provide is the basic building blocks required, such as a firewall service, load balancer service, virtual networking, layer three isolation, layer two isolation. And using these basic building blocks, providers can stitch the services, basically define a service templates, and publish them into the catalog. And not only they specify what are the features of those network services, and they can also specify whether what are the quality attributes, what are some other attributes they can specify. And they publish that into the catalog. And when these services are ordered, we orchestrate these services by mapping these logical network features and looking at the actual infrastructure, what capabilities are there. So based on that information, we map these logical networks into the operations required to be done on the actual physical network. So your network infrastructure may have a physical appliances or the virtual appliances. So we understand both of that and map with respect to what service design specifies. So once the services are designed and deployed, so we use our service management engine. Since our nCloud X orchestrated the services, we exactly know where those services are provisioned, which devices we have picked, which interfaces we have used, what are the logical resources we have consumed for that service. So we have the complete map. Using that information, we use that information basically to manage those services. Such as, let's say, if there is an alarm at the network side or there is a device down or an interface down, we can map that into what is the service that is getting affected by that alarm and generate a service level alert. And we can also map that basically which tenants are going to be affected by that alarm. In addition to the service management engine, we have a capacity management engine which monitors the network capacity at real time, whether they are the logical resources or the physical resources. And we provide the threshold base to alerts to so that if a particular resource consumption is high, based on the thresholds that are set, we provide those alerts. For example, a gold service requires a firewall. And if you run out of the firewall context or you reach a certain threshold, we will alert the administration. And also, we provide a network-wide health monitoring, pod-level network-wide health monitoring. Using this information, it will enable the providers to optimize the network utilization. So that briefly talks about the features that we provide. Now let's look at the integration that we have, especially with the OpenStack. So we have developed a quantum plugin using the Grizzly release. We haven't yet published, but we're going to publish it in the Havana cycle. And we have a demo actually we can show how we integrate with the OpenStack. So here is one example of how we map the OpenStack use case, networking use case, into our service design. Here is a simple example of a flat public network, specified by OpenStack, one of the use case. So it can be represented into nCloudX as a container which has a public zone and a virtual network. Let's look at the little more complex example where there is a private network required for each of the tenant. And each tenant needs a private outer space, too. So that particular requirement can be represented in nCloudX by using the diagram that I'm showing on the right-hand side where there is a public zone and a private zone. And where the private zone has a firewall and L3 isolation to which virtual networks are connected. So I just want to highlight what we bring to the table with the OpenStack and nCloudX together. It basically completes the whole solution. So it is a complete solution to offer the storage, network, and compute. And in addition to that, we offer using the nCloudX providers can define the network services they want to offer and exactly control how those network services are going to be provisioned, which part of the data center location. And they can offer differentiated services. They can offer quality of service. They can put quality of service attributes to those services and also some security policies they can attach. So using OpenStack and nCloudX, so they have a complete control on how the network services are going to be orchestrated and what part of the network. And we provide the complete visibility. And to summarize our product, one of the main differentiation is we work with the existing infrastructure. And we provide the service design capability and that can be deployed. And we manage the complete from layer 2 to 2 layer 7 on a multivander network. And also, we support various form factors like we work with the physical appliances as well as the virtual appliances. And we also support some overlays. We currently support VXLAN. And we support capacity management and service monitoring. So essentially, it provides the complete network lifecycle management, which starts with the network service design, deployment, and then the management. Thank you all. And if you have any questions or you want to see the demo, we are at booth C26 there. Thank you.