 Hello team, my name is Anshul Bahel and I'm a technical marketing manager for the Ansible Automation platform. In this segment we'll shift our attention to deploying the CoolStuff app to the Edge devices. I'm acting as the release manager for the Edge deployments of the CoolStuff tour. Business is expanding for our CoolStuff organization after the launch of our website and these are exciting times here. Based on our recent success, we have launched two retail stores for CoolStuff in Johannesburg and in Dublin, which have self-serving kiosks located in them where customers can visit and order items available in the inventory. My job is to make sure that kiosks are always up to date on the inventory available and always have the recent version of the CoolStuff store running on them. In our Edge deployment workflow, we have automated the configuration and deployment of the CoolStuff app on this kiosk through Ansible Automation platform. As an organization, we want to make sure that all these devices are running a standard configuration and we want to reduce the time to deploy IT resources when expanding or relocating. As we have recently updated the CoolStuff application in the previous demo, we also want to deploy the new CoolStuff app on this self-serving kiosk. Let us first check what is currently visible on these kiosks. There are currently five kiosks in our Dublin store and three in the Johannesburg one. We have the web addresses of the kiosks number one in Dublin and in Johannesburg visible here and they are showing that they are out of stock on the Red Hat Fedoras. The image of the Fedora SKU seems off as well and we have new styles of Fedora available now. Let us try to deploy the app on this kiosk with a new image and a refreshed stock. We have designed an Edge pipeline that updates the app deployment on this self-serving kiosk. I will trigger this pipeline that starts an Ansible automation work. This is the automation controller component of the Ansible automation platform. It acts as the central hub for automation of a kiosk system and can automate multiple types of systems for us. Whether they are on-premise or multi-cloud deployments, it can also automate network and security devices or the devices at the Edge in this case. You can divide automation tasks into job and workflow templates. Work templates are Ansible claybooks that hold a set of automation tasks for target systems and workflow templates are a way of organizing the job templates in a desired sequence. In this case, we have a cool stuff store as deployment workflow that we use for configuring and deploying the app to this kiosk. Our Edge pipeline triggers this workflow for automating this kiosk. If we check out the workflow visualizer, we will see that the job template to configure and deploy the app on Dublin and Johannesburg stores are attached to this workflow template. Ansible claybooks or job templates are item-protent in nature. This means that this automation run will configure all the Edge devices in the same manner and if the configuration on some of the devices is off, it will bring them back to the desired state. If there are new kiosks that are added to the store, this will configure them to run the course of the app as well. The automation controller has a concept of dynamic inventories, which we have set up for the Dublin and Johannesburg stores. This means that the automation controller will always be aware of the kiosk present in the Dublin and Johannesburg stores. If we add more kiosk to the store, the automation controller will update the inventory before an automation run to make sure it's configuring and deploying the app on the new systems as well. This is the topology view for the automation mesh. Automation mesh is an overlay network intended to ease the distribution of work across a large and dispersed collection of workers through nodes that establish peer-to-peer connection with each other using existing networks. It provides scalability, reliability, and security global automation happening for the coolest of organization. To its bi-directional communication layer, native pairing capabilities, and TLS traffic encryption. For this deployment model, we want to make sure that the automation is executed close to the Dublin and Johannesburg kiosk devices for a reliable automation. In this topology view, you'll see that the Dublin and Johannesburg stores have their own execution nodes, which helps in scalability and a reliable automation close to these edge devices. We can check the health of these execution nodes from here, and pairing capabilities allows for a reliable automation in scenarios where an execution node is not reachable. It will automatically fall back to the next closest one. We can see that the job templates that have the inventories and instance groups attached to them. Then make sure that each job template will use the closest execution node and automate the target host that are in that store. So for the Dublin deployment, we see that the Dublin inventory and the Dublin store instance group or execution node is attached to this job template. This makes sure that execution is happening close to the Dublin node and the devices that are getting automated through this job template are only the Dublin kiosk. As a release manager, I want to get notified through Slack if the edge deployment pipeline has started and what is its status. For this, we have set up Slack notification message and attached it to a deployment workflow template. This will notify us about the systems that are configured once the job run is completed with their web addresses. Let's see the job runs now. In the job runs, you can see the logs and check if configuration and deployment of the app on the kiosk happened as we intended. So we can see the logs of what happened in this job template run. As we can see, our workflow is finished now. Let's check if there were any new messages on our Slack channel and also check if the kiosks are updated with the updated inventory and the new image of the Fedora. As you can see, the job run configured the kiosks first and deployed the new Cool Stuff app on the kiosks in Johannesburg and Dublin. By clicking the web addresses of each kiosk, we can see the job run configured all the kiosks. The addresses of the kiosks show that they were updated with the new application because you can see the new Fedora image as well as the new updated stock. I'll hand it back over to Ian for his segment.