 Hi. So today in this video, we will be doing magma deployment using M-COP and managing both Orchestrator and Access Gateway remotely with the help of M-COP. So as a deployment strategy, we look forward to use M-COP and Magma Controller placed centrally in some sort of cloud provider, GKE, AWS, or Azure, whereas the sites at Edge would be running Magma Access Gateway, which essentially would be managed by M-COP itself, along with some of the other cloud native applications running locally at those Edge interfaces, where M-COP would be responsible for managing the deployment itself using Kubernetes API, deploying Magma Controller on the local cluster itself, and Magma Access Gateway on the remote cluster, interfacing with the Magma Controller using rest interface, using which we would be triggering the registration request for access gateways that has been deployed using M-COP. And another interface potentially we can have with the Magma Access Gateway to fetch the hardware ID and challenge key unless it starts providing a mechanism where we can pre-program hardware ID and challenge key as part of the deployment itself. So from a registration prospect and the required configuration, we assume Magma Controller is already deployed with the relevant certificate and the CBA has been created, providing the admin key for a certain key for operator. Then followed by an access gateway what let is provisioned with the required config and search as part of Day Zero configuration. Hardware ID and challenge key can be fetched as once the deployment is done, which results in triggering the CBA, doing config assign and config deploy, further merging the config templates and parameters, forming the relevant AGW registration request, which is further sent to Magma Controller over the rest interface to essentially program the access gateway in the controller, after which the access gateway can check in into Magma Controller and initiate the bootstrap process. So since this is still work in progress, so we will be showcasing today the deployment part only, where we will be deploying the Magma Controller and access gateway with the Day Zero configuration. And the portion of automation of AGW registration is not yet available, so we would be triggering that manually. So switching to MCOP UI. So we have two clusters, one is the host cluster and other is KOD cluster, which we will be using as a remote equivalent for deploying access gateway. And we will begin with creating the services and deploy the access gateway. So first of all, we will need SQL-based databases so that are consumed by Orchestrator and Orchestrator UI. So to simplify our deployment following the guide documented by Magma Community, we would be using two separate databases, MySQL and Postgres SQL, followed by creating a service for Magma Controller, which will include Helm charts for Orchestrator and override profile that would be including the relevant information of certs that we will be using for this deployment and all other overrides we want to potentially do. Then we will include LTE extension on Orchestrator that we are going to use for this demonstration and create all the three relevant services followed by we would be spawning instances of these services starting with SQL. So this is going to be on the host cluster. So let's create the instances before instantiating them followed by instance for Magma, which is also going to be on the host cluster. OK, so all the service instances are created and if you switch to the cluster, currently we do not have any pods. So we'll start creating the databases first. So both SQL and Postgres SQL are being created. So let's instantiate Magma, which is instantiated. We see the corresponding pods are being created. So with all the pods running now, we should have access to the NMS UI. So this is the domain that we chose. So I'm logging to the master instance of this one. So this help chart by default creates the user as part of the deployment. So this is where we will continue using master instance and they'll just enable NMS access. So if you see we do not have any network configured. So we are starting with the blank slate. So we'll add a network first, network underscore one. And we are going to be using network type LTE. And however, do not have any access gateway yet. So we'll begin with the access gateway creation as this is where we will upload the Helm chart for HGW worklet along with the override profile. And now we'll create the instance for this access gate. So this is going to be deployed on the KUD cluster, emulating edge and access gateway requires dual interface, one towards internet where it will be connecting to the Magma orchestrator and second, as a provider network, providing connectivity to E node B. So we have access gateway instantiated. So in the KUD cluster, we see the worklet has been started. So we'll wait for access gateway to come up. So we can fetch the hardware ID and challenge key to register it against the orchestrator. So in couple of minutes, worklet will be up and running. So this is where we will fetch the hardware ID and challenge key from. So let's call it worklet gateway. Gateway 1 hardware ID version it will auto-pick and the challenge key. So we have the gateway created. So now, usually you would have proceeded with configuring the access gateway. So we don't have to do that because the configuration and the root CA certificates are loaded up front. So all we are going to do to monitor is whether the status of Magma check-in goes through fine. So we see that it has already bootstrapped successfully. Shortly, the check-in should also go through fine. Yeah. So the check-in is also successful. And if you see the health is good. The last check-in has already been done. And that concludes the demo. Thank you.