Getting started with Crosswork Workflow Manager​

Oh, I see some people are still joining, so let's give it two more minutes maybe and then and then we kick it off.00:00So, thank you everyone for joining. If we can start the recording, please, will help a lot. I'll bring up my camera as well. Hello recording is running. Okay thank you.00:18Yes yes Christian Neil it's because this is a webinar, the way it works is if you want to ask a question, you know, maybe towards the end, you can raise your hand and we will send you an unmute request.00:41And you will you will be able to unmute and ask your question. It's a different format than than, you know, the traditional Webex meeting, this is a Webex event because usually the audience is big, so, it's a way to kind of keep.01:00Focused on the topic while, interacting with you mainly on in the chat. I will also have two Slido's Slidos during this this presentation, so.01:19Yeah participation simple questions just to kind of understand where you're coming from. But with that being said, topic for today is workflow automation. This is a series of three sessions. It's the 1st time.01:36When we're running it, so any feedback is more than welcome. Today we're gonna just go through the basics. This is, you know, we to get us started in understanding what workflow automation is, you know, which flavors you can consume it or install it.01:56In your environment, we're gonna look at solutions and a basic workflow. 2nd session will be focused on building workflows, and David is who's in the call today with me is gonna present that session and he's gonna focus on.02:16And the components of a workflow, you know, what do you need to customize to implement a customized scenario? It's gonna talk about adapters or ways to interact with other systems or with different parts of your infrastructure. And then the last scenario, the last session is going to be.02:36Workflow automation in, in the real world. This is going to be delivered by Georgio and the goal is to see how workflow automation would work with other systems and I'll leave the surprise for, for that.02:57But that's going to be also an interesting, an interesting one. If you wanted to register to any of these sessions, you have the QR code in there. I'm gonna bring it up at the end again, and hopefully, you know.03:17This session will be useful and you will decide to continue the journey with us. Okay, so today we're gonna talk again about workflow automation, ok? My name Ispike. I'm part of the adoption team within Cisco. David.03:31And Georgio, you know, we are in the same team. Our focus is to work with customers that have decided to invest into Cisco products and help them understand what the product is, what capabilities are, you know, keep the customers up to date with new release.03:51And what they bring, show the basic scenarios, show, you know, the out of the box capabilities, and bridge, you know, between the sales and the implementation. That's mainly where our focus is. So.04:11The agenda, it's going to be focused on some basic concepts for for workflow automation. Then we're gonna look into the three prebuilt solutions. Excuse me, and.04:31We're gonna continue with building a workflow and there is a reason they are one, one after the other. And you're gonna see through the presentation. I'm gonna use the workflow designer, and there is a note to that which I'll come back to during the presentation at the beginning actually.04:51Then we're gonna go back because there is a demo which takes some time, so I'm gonna start at the beginning, we're gonna go and see the results towards towards the end and then we're gonna, we're gonna close it. It should go around.05:121 h 15 min, give it or take, so, and I hope I'll be able to you know fit within that window, and that should leave some time for questions on the end. If not, you know, during the presentation, feel free to put your questions in the.05:27Chat my colleagues will help take care of them and answer.05:46So, when I think about workflow automation, it's, it's like I'm thinking about, you know, a chef, and, you know, you can have like your personal chef or a 2047 working chef.05:51And the way you develop it or you make it, it can be like a common, a common chef, it can be a mission install shift or it can be like a personal chef, right? So that's the flexibility that workflow automation needs to bring.06:11It does need it it does come with, you know, out of the box recipes, which we call solutions, and it also comes with the ability to customize, right? And that will require to use either the, the designer that I'm gonna go through a bit today, but also it will.06:29Would require to have some knowledge around the workforce specifications language. We are using the 0.8 specifications for serverless workflow. So.06:49All of that it's built in. I'm gonna show you the code part. I'm gonna just how it looks, you know, how it works and then the designer and we're gonna focus on the designer because this was introduced recently and the goal is to bridge the gap, like to help quick start you know the customization.07:10Of some of the built in solutions. Excuse me.07:30Okay, so, what it does, so like I was mentioning like for me it's like a chef, right? So basically the goal is to take procedures that you have already created and maybe you are using on a day to day basis, right? We call those, most.07:35Most of the time methods of procedures or mops, and take those procedures and put them into something that is repeatable, right? Something that you can you can see how it progresses and then you also have a trace that you can leverage and use in case you have to to to do it on.07:55Audit right or to you have to make sure that everything went accord according to to plan.08:15The way this can be installed, and this is something that I want to, kind of clarify, right? Because, I saw some confusion discussing with, with some customers. We have the same product.08:23Which is, you know, a cross work workflow manager, yeah, which is in here and this product can be consumed if you have CNC, right? And in CNC it's a module, and you will find it in here in device management.08:38Workflow automation in this too. But in some you will see the CWM, so that's why I want to clarify CWM comes from crosswork workflow manager. But it can also be consumed as a standalone product, ok? Which is called crosswork workflow manager, right? So again, we have a CNC workflow automation.08:58Right or for automation module inside crossword network controller CNC, and then we have cross workflow manager, which is it's a standalone product. So this addresses both situations where, you know, some customers, they want everything into one tool, right? And some customers.09:18They had one everything in one tool, but also they have teams that would just like to use this independently. And then the 3rd customer which just wants the workflow manager as a standalone product and integrate with different other tools that they already have in, in their environment.09:38So I hope I hope that kind of clarifies what this means. So this is the 1st slide though. I hope you're used on with how, how it works, but just to get an idea on where you are, because there are some differences.09:57If you can like pull up your phones and just scan that QR code and just select one or multiple, of these choices just to get you know a feeling of what what are you using or if you're just planning to use workflow automation.10:14There we go, thank you.10:40Okay, that's good. Now it's giving me some time to get rid of a dry mouth. Okay.10:59Thank you, thank you for participating. Really appreciate it. Let's give it ten more seconds and then we can continue. Good, so I see the majority is is looking to learn more in this session. That's.11:16Good they are in the right place. We built this series just with that in mind to get people started. But I see also that we have.11:36People that have 7.17 .2, and they also have the standalone version. Okay, good, that is good. Okay, so let's continue. Thank you very much for participating. Really appreciate it. So why is that important? Let me just go and see if I have.11:49Yeah, so I'm gonna go to this one 1st. So why is important, right? So.12:09Today we're gonna look at the workflow designer and this is something that was added in 2.1 and the module inside CNC 7.1 e.g., is version 2.0.12:15Which does not include this workflow designer, right? And this is something that we run into you know with with some customers and there are some capabilities in there that really allow you to do drag and drop and build a workflow basic or something more advanced like this, yeah?12:31What you also don't have in 7.1 or in CWM 2.0 is an interface, a UI for golden configuration, which is 2nd solution and also device migration use case, right?12:52So these two have gotten like a user interface and you're gonna see, you know, how that looks like which really facilitates on you know how to how to use them and to.13:11Configure them in Owen and to run them. The other thing is that we have cross work assurance which was called PCA before. This is an acquisition that happened a couple of years ago or one or two years ago.13:25And it's the accident team and basically this is doing assurance at the hardware level at the link level where basically you can use specialized sfps to track to the mini to the millisecond even even lower.13:44The availability and the properties of a specific link, a critical link, you know, think about connections between databases sorry between data centers or critical one links and so on. Our colleague Marcos has delivered a three.14:02Action series on crosswork assurance. The recordings are in the community, you know, feel free to to go through them and to to better understand the product, but it's a very, very useful product. So with this version, we are adding the integration between between the two, right, so.14:21PCAs or cross work assurance as it is called right now.14:41And CNC or CWM. Okay, so let me go back ok so we had ok so as I mentioned, you know, this is to me, this is our, this is like our chef, it's able to use multiple.14:45You know, create multiple recipes and use all kinds of ingredients. That's the way CWM is built, right? So we have on the, on the left side we have the integration, you know, with.15:05Different systems, right? And we use adapters for that. So the systems can be something like NSO, it can be a ticketing system like we can see in here we it can be the integration with different components of the infrastructure.15:23Just to be able to communicate with them, it can use brokers, right? To integrate with other systems and this is what we added. We added, e.g., recently MQTT for for Webex and PCA. What it provides is.15:411st of all, I keep stressing this, a local designer, the ability to create operated dialogues, meaning forms where you can get input, right? And that input then becomes part of the variables that the the workflow is used.16:00You we have the pre built use cases. This was already in there but it was enhanced and I'll mention some of the enhancements.16:22And that, as I mentioned, the user interface for the golden config and device device migration and then the integration and I already mentioned mentioned that. This is something that in 2nd session you will be seeing more, you know, about the adapters.16:31And, yeah, I'll leave that for that session so not waste more time.16:51Okay, so how to think about a workflow or how to think about a solution, right? Because these are two concepts. So what we have in here is actually is a solution, right? So, sorry. So, the way it goes is like this.16:57At the top is what we call an application.17:17And in the case of solutions fleet upgrade it's an application basically. And what does that mean? That means that it consolidates all the needed components to be able to run a fleet upgrade, right? And inside we have a mop.17:20Inside is all method of procedures inside a method of procedure procedure we have different actions, and which can be, you know, run before the you know the actual act the the actual procedure, right? So checks before.17:37Four, then run the procedure checks after. And these stages can be, you know, 354, you can choose each other choice. For the fleet upgrade, e.g., we have a pre pre checks, you know, distribution stage, activation stage, commit stage, and then the post check.17:56Inside the stages or the mops, we have the mob actions. And the mop actions basically define a single step within your procedure, your method of procedures, right? It is focused on one.18:17The the best is to get the simplest step possible, right? Or to divide your operation, your procedure into smaller.18:37Very simple steps and you capture that into a mop action. And you can see that the last piece, which is the smallest component, if we can say that, it's the workflow, but actually in here this should be like an equivalent because a mop action it's actually a workflow behind, right? And, the reason why the.18:48This is important, it's because this, so if we go the the other way around.19:07This is where you put your customization. After you do your customization, the moment you turn it into a more action, this becomes reusable. And this is the way we achieve that point where you can reuse a workflow over and over again or go back to the workflow.19:15And improve in case there was some some challenges, right? A more action is part of.19:35You know the method of procedures in different stages, which is addressing a use case, which is actually the application, right? So I hope kind of that helps kind of build a mental model on how this looks like. You can think of an onion if that works for you.19:40And this would be like the the core and this would be like the auto shell and everything in here is like the actual onion. Ok. In the workflow, right? We have different, sections, right? That define the the workflow. So we have states we.19:58You have activities and then this states and activities when a, a mob is run or an application is run are passed to a process inside CWM, which is a worker.20:18Which will start the implementation. The moment it will start the implementation, it will look for how do I connect to that device, how do I connect to that system? And that's what we use the resources for. So that's where we define the connection profiles, and in order to be able to authenticate with different.20:34Resources then we have to keep the secrets right outside of the workflow as a best practice always. So there's a secret section where you define the secrets and then you just reuse them or you call them inside inside the workflow, ok? So the centerpiece in here is the worker which takes the worker.20:54Flow contacts the resources, uses the secrets and executes whatever was defined in the different stages, ok? So I took more time on this one because I really believe.21:15This hopefully helps build the mental model on how this works because we're gonna see it during during the demo. Ok, so I'm gonna skip this one because we already talked about. This is for your reference, so it's a small.21:27Dictionary of different words or key words that you will hear, so you already heard about workflows, a job, it's like one execution of a specific application mop mop action. A form is the interaction, the adapter already mentioned, the activity.21:46It is what you design inside design inside the workflow.22:05The worker, the secret resources, I mentioned already and then we have events. And events are the way to communicate with a different system. So if you think about the ticketing system, you would use an event to send information and open a.22:11If you want to call another workflow inside the workflow, you can use an event to trigger a sub workflow. If you want to send a message to something like Webex, you will use an event and you will use an adapter.22:31And through that you will be able to contact Webex and, you know, have an interaction and I I believe David is gonna show that in 2nd session. So what actually happens when we click run? So e.g., if we take fleet upgrade, right? When we click run there is a suite of.22:45Of, steps.23:06Basically screens, which will walk you through the the preparation before running the workflow. It will ask you what device do you want to do? So it's a form, it's a suite of forms, right? So that's the way to interact with the operator because there are two.23:10The personas in here. So there's the persona that designs the workflow, and then there is the persona that.23:29That operates the workflow, ok? So the form is built mainly for the operator. So the person the persona that will do the upgrade, let's say or, you know, check if the golden configuration is if devices are compliant.23:38With the golden configuration. Then we have the job, the worker adapter and device, right? So this is something that I already touched on.23:57Okay, good. So now let's talk about the pre built solution because I have to start the, the upgrade as well and that's gonna run for about 4040 plus minutes. So 1st we have the fleet upgrade.24:05Oops, what's going on? So 1st we have the fleet upgrade, which is focusing on creating upgrades, sorry, it's, it's focused on doing upgrades at scale.24:21Basically, right? So you can define an image, you can define a policy, you can combine and divide define something which is called a golden ISO. It works with Cisco devices. We have this so it can be adapted to other vendors, there is.24:37One specific device that it's already built in from Juniper and MX 960I believe. Probably others will be added, but the procedure it's it requires a discussion with with our services team or delivery team, in case you are interested to add specific devices in there, right? It's an effort that will.24:56Goes back to the business unit and it needs to be a collaboration and you know there is some investment. Then we have the golden configuration.25:16Where you decide the standardized configuration that you have on a specific type of routers and what the system will do is it will check and make sure that NO devices are compliant. This avoids the situations where people go out of band and do some changes on the CLI and those changes.25:25Do not get captured or we are not aware that they happened, right? So in this case you can use golden config to kind of keep the standard where it needs to be and but also be aware, you know, what devices different changes have been implemented. Then device migration, it's something that.25:45You have a user interface, but there is NO standardized way. It's very tough to define a standard, right? So this is a bit more complex. It requires customization from the beginning. And actually today we're not gonna talk too much about that one I think it requires its own its own session, but the.26:04Goal here is think about, e.g., when you have a device that you want to replace either because it has some issues or just because you're doing you know like for like replacement or you know you're doing an upgrade. In device migration, you can, you know, capture the.26:23Current configuration, i'll set the new configuration, but also be able to implement some logic that would track the devices that are directly linked to that specific device and that goes into the prechecks and all the post checks. As I mentioned, this requires a bit to be a bit more advanced.26:43Most of the time it's a work together with with our services team as well.27:04Okay, so, let's actually go and kick off with upgrade and with that, we'll also have a look real quick at, at the user interface.27:10So let me go into the let's refresh this, make sure that we are still connected, ok.27:24Okay, so this today we're gonna use CNC. So CNC with workflow automation module inside, right? If you guys need to see a demo on CWM so we can create like a session specifically focused only on CWM, please put it in the chat. We'll take that into account and.27:40Will create a session just for that one, but the.27:59The functionalities are exactly the same. There is a small difference into the menu, right? Because this is just a module inside CNC, whereas in CWM you have like its full dedicated user user interface, ok? But the concept are the same, the way the solutions that.28:04Bit upgrade and soon are being used, it's the same, the designer and so on.28:24Okay, so what we're gonna do now is we're gonna go and just kick off with upgrade. So I'm gonna stop with this one because again it needs to run for a while.28:28And let's go like this. So 1st of all, let me talk about the image repository and the software conformance. So what we can do in here is we can have a local repository or we can have our connection to cisco.com. Now in the local repository.28:47So to do an upgrade, you will need to have the image on the local repository, right? The connectivity with Cisco.com all allows you to synchronize the catalog, right? And always be up to date with the latest updates, right? In, for ISXR, e.g., we call them smooth, soft.29:06Where maintenance I don't even know what the U stands for.29:26So, ok, so which are like updates, and there is a particularity with these updates that, you know, you have the 1st version of a smooth and you have 2nd version of a smooth, the 3rd version and so on and so forth. And they are incremental, right? So 2nd one.29:33One includes everything in the 1st one, the 3rd one includes everything in the 1st one. So if you select the two.29:52Then you run into a situation where you will apply the same things twice, which is a waste of time or it can also create maybe maybe some issues. So this is built now into one of the capabilities that was added with 2.1, where if you select two.29:58Smooths that.30:19Are consecutive e.g. or you know the 1st and the 3rd one, it will automatically identify that and remove the lower one or the earlier one and keep the latest one only and I'll I'll show you, I'll show you that. But that's important because it removes one, let's say possible.30:21Delay or failure that could eat into your maintenance window. Now what we have is software conformance, and software conformance means that based on the images we have in the repository.30:41We can create a policy, right? So I have a policy in here. E.g., this policy was created, which is saying that, you know, a virtual XR nine K should have this specific version, right? So I can select the.30:54Questions in here and this specific software package, right? So this is a smooth applied with it, right? What this will do when we go and we run a conformance report, so e.g., let's run this.31:15Okay conformance. Okay, so we select this policy, ok? Here we go, and we say create report.31:35And what it will do now, it will go and scroll through the inventory. In the case of CNC, the inventory it's the same, right? We have the advantage that CNC already builds the inventory, and it will come back and.31:52And say if it's conformant or not. Now, I did a mistake in here.32:12It should be let me see. Let me go back, let's do this. So test two select the policy.32:23And then create report. Let's try that again. I hope it's not what I think. It's conformal, ok. So, that means that the upgrade might already be applied. But regardless, we're gonna just go through it. I was playing yesterday with it.32:38But let me see this one ok we can see it in this one it's saying it's non conformant, it's missing one package, so basically this would be the result, right? It would say it is missing this specific small, right?32:58So let's, let's come on go away. Okay, let's go and start the upgrade. Let's go to this with upgrade again, start with upgrade so in our case we gonna use this specific.33:16So we keep it reserved just for this specific demo. Let me move my face, go next.33:36The way we're gonna do it is we're gonna apply an update and not an upgrade because usually an upgrade takes a long time. So, let's see we're gonna apply this one, ok? And here is what I was mentioning like if I select multiple.33:48E.g., so I select all these moves that I already have in my inventory and I click on optimize. What it will do, it will say this one is removed because it's superseded by one of the other packages, right? So it will automatically do this for you.34:07So right now let me go back. Let's take this one.34:27We'll add it, go next, we will select the mop. So this is created specifically for upgrading the XR nine K And these are the stages that it will go through, right? So we have a pre stage, we have ten steps for those stages, it will check.34:31If it's online, to check the activity, it will analyze the the logs. It will look to see what packages are in there.34:51It will capture the command that so it will run some commands that will run beginning and then at the end and after it will do a diff between and it will show it at the end like what are the differences between pre and post the upgrade.35:04Then we have, checking the space, it will upload the image, it will start activating it committing it, and then there are other post checks, which again it goes for to check for, for health, one that once that is validated, then it will go to some of the same steps that it will.35:21Going to at the beginning just to be able to do the comparison and validate that the upgrade was was successful.35:41So let's put this test today It's november accepted failures, so you can run up to 100 devices in parallel with version 2.1. On 2.0, you can run up to 50 if I'm not mistaken.35:49Out to that, you will, you will be limited to 20. So we kept improving the performance. Running 100 devices in parallel or when I say 100 devices, right? In this field you can decide how many devices can you accept not being a.36:08That were having an issue before the entire, you know, upgrade sequence is stopped right for for all the devices. So, you can remove this and just let it run even if there are NO failures, or you can set this to.36:28To, you know, a number that is acceptable to you.36:48Then we can schedule the entire workflow one to run, but also we can schedule this per stage. So you can see the the five stages in here. So e.g., you want to have a maintenance window where you just or you, you're comfortable to do this outside the maintenance window.36:52Where you distribute the images, so you make sure that the images are already on on the devices. And then when you have your maintenance window then that's where you do the activation, the commit, you know, and the reboots if it's needed and you know you check the the success, ok? So right now we're gonna just run into the right.37:12So we have a summary in here. We're gonna just run the job and what it will do, it will start It will start the upgrade, ok? So let's go and and have a look.37:33Yeah it's just starting so let's get it run, there you go. So it's already started let me move my face.37:48As you can see, it started with a pre stage, right? Now it's doing the note, not check. If you want to see what's actually defined in that action, so this is a mop action, you can go directly into into the workflow. So let's actually open that just to have a quick look.38:04And it will continue, you know, to go through the the the different stages. So we're gonna let this run.38:23And we're gonna come back from time to time to to see how is it going, ok? Actually let's see. So we can see like in that specific stage this is like you know the entire trace so the audit if you want. It will capture everything that is.38:29As part of all those tests. This is something that you can export as well. If you want, you can, you can download it in case you need it for audit or in case you want to put it pull it into another system and and maybe have further analysis. The other thing that you can see is in the input you can see exactly.38:49What it is using as variables or you know information or details in the form of key value pairs. And then what it will output before what it will output and pass to the next next stage, right? So this is what the result is.39:09So it looks like the notes.39:29Check passed, this was marked as successful. So this message is going to be passed to the next, to the next stage and you can see that in here, right? So it's already going through all the different stages. Yeah, so this is gonna, you know.39:33Work its way, we're gonna come back to it. Okay, so, let's go back to the basics while this is running.39:51So what do we need to actually get to have an application like this, like this entire procedure, right? Because this is a procedure, yeah.40:08So, the 1st thing that we need to think about is, ok, how do we enable the connectivity in a repeatable way, yeah? And that's where we start with secrets. So this is where we define different secrets. E.g., I have one.40:23For a specific device on ASR 1001 that I'll be using to build a workflow. In here I am we can use different means of authentication. What I'm using in here is just basic authentication, right? This is gonna go through. So now we have to.40:44Tell it, you have to go through restconf. And that is something that we define in resources.41:03So, if we go into resources, we create our router and in here we can choose different adapters, right? So these are the adapters. In this case we're gonna use the genetic rest resource. This is version two, right? If you are on two zero, this is gonna be.41:10Version one. And by the way, the versioning system is available and valid for all the workflows, right? So that means that.41:30If you have a version of a workflow that you've built, you can create a new a new version of it and they will be kept independent one of the other, which means that it will not affect whatever procedures you already have in place and you know that work.41:40And you can use that second version to, e.g., do testing, right? So e.g., you've run into an issue and you recoded that inside the workflow, then you can use that new version to go into the test. Once you are comfortable with that version, then you can just go back into the mops and just.42:01Switch the version and select a new version. That way you shift your entire procedure easily to to the new to the new way of doing it.42:20So in here we have the adapter, ok? We set the data type. In this case, I'm going straight to a specific device, and that's why I'm giving it like the the IP address. I'm using HTTP, and in this case I'm not using certificates or anything like that, so that's why I can copy.42:31The insecure connection.42:51If you want to go to multiple devices, then what you would do is you would select a you would go to NSO, ok? So you will leverage NSO especially in CNC that's built in, and through NSO you would be able.42:54To use the calls towards NSO to address multiple devices at once. There are other ways, but that it's the the simplest one.43:12Okay, so let's go back so we we send the resources. Now let's have a look at the adapters, so the adapters again it's the connection with the different devices or to different systems. So in here we have, the one for rest. This one is for NSO, e.g..43:24You can have an adapter towards email and there is an adapter here that goes through Webex, but can be to teams. You know, it can be to whatever you need. And the way it gets configured, e.g., if I go into one that I am using right now is I am telling it.43:45These are the allowed activities that I want you to use. Actually, it's gonna be easier if I can show you directly in here. Oh, sorry, nothing here.44:04Go back. No, NO NO. This is something that probably David will go through. What I wanted to show was in the workers, right? So in the workers we have, so the worker is the.44:14Subsystem that actually runs everything for you. So e.g. if I go to rest, I can see in here in the worker what is allowed to do, ok? So, I can select anything from here and add it to, so e.g. I'm not gonna play with it because it's.44:30But you can, if you want to add Webex, you just add it in here, right? This is pre built, ok? If you want to add email, you can add it in there. In this case, this is only designed to use REST conf and connect to, you know, directed to devices. And once you select it, you can choose.44:51Use what.45:11Calls it is allowed to do. So it can do you know if you don't want it to be able to delete patch or if you wanted to only be able to extract information, then you just give it a, a get and that's it, right? So what I'm trying to say is that you have the flexibility.45:15To choose what specific workers are allowed to do. And that is important because you can have, you know, multiple smaller workflows that you defined and that you reuse or call inside, you know, a bigger procedure, ok? And for those work, for.45:34Those workflows you can connect them to a dedicated worker that is limiting the actions only to getting data, right? So using it, e.g., only to collect some information.45:54Okay. Okay, so these are the workers again recap secrets, we define how we connect resources. We define how we use the secrets and the adapters and to what purpose. So in our case it's gonna be directed to an ASR 1000.46:06Adapters are the way to connect to, devices or ticketing systems, right? So this is extremely flexible. They can be created from scratch or you can use what we already have in there. And then the workers is your execution system where you have the ability to.46:26Limit right, what a workflow is entitled to to do. Good. The last piece, you know, the last two pieces, right? We have event types. So event types is where we define.46:45How do we interact with 3rd party systems, ok? So we have in here two which are predefined, and we can see in here that we have different predefined resources, right? That we can select from. This specific one mob status.47:02And the mob action itself is what makes a workflow available inside a mob or it transforms it into a mob action basically. So I'm not gonna stop too much on our events. This is again it's a session of its own, but just keep this in.47:21In Mind that when you want to trigger another workflow, you're gonna use an event.47:41As a trigger another workflow inside an existing one. When you want to trigger a ticket to a ticketing system, you will use an event. When you want to interact with something like Webex, you will use an event to generate that.47:46Okay. And then the bigger umbrella, it's again application types. And in here we have the predefined ones, right? Upgrade device migration and golden config. You cannot modify these ones, but you can clone them, ok? You can clone them and make them yourself.48:03And then you can create custom ones. This is again a capability that was adding application types. This is something that was added in 2.1. So you need CNC 7.2. And you can define whatever you want, right? So, in this case, e.g., I have an application.48:21We're gonna have just three stages and what this does is basically going to, you know, this same ASR 1000, which is our guinea pig.48:41And it just sets a description on an interface and it brings it up, ok? So it's a very simple scenario that was built from scratch and it can be built from scratch and then captured up to an application.48:52Which we're not gonna go through, we're gonna do something a bit more simple today. Okay, so, let me, let's go back, let's see how our upgrade is going.49:09Let's check. Let's see. So it's running already for 11 min. We already finished the prechecks. Okay, we can go and have the details. Oops. Yeah, this is like a bug that I I recorded because so we have introduced the.49:25The dark team and in the dark team unfortunately the in this section the the code is not showing properly. So we can see in here.49:45Interface summary, right? So we can see all the interfaces on the on the specific router. As you can see, so it's getting some output from the commands just to prepare for, checking the same after and then doing a diff between the two. Now it's at the stage where it it.49:56Check the space, the disk space, so it validated that it's enough, and now it's just gonna copy the image, right? So this is gonna take a bit of time.50:15So we'll let it, we will let it continue to run and go back to two workflows. Okay, so let me just go back to this a bit just to make sure that I haven't missed something.50:24So how we've already talked about the stages, we talked about the image repository and the conformance reports. Actually I'm gonna go back to that one a bit and then we started the upgrade. Okay.50:44So let's go to, let's go back to this. Let's go back to, fleet upgrade. I just wanna show.51:00Another feature that was added or capability that was added in, in 2.1 and 7.2, which is golden ISO. So basically what you can do with this is you can, let me move my face again.51:19You can select a specific device. So e.g., we have the NCS in here. I'm not sure if actually that's gonna be the one NO and we gonna select this one.51:39It's gonna present us with, you know, the available smooths, software maintenance window, thank you Georgia for upgrade, software maintenance upgrade.51:54Okay, you can see that it also mentioned right if it needs to reboot and you will see this in the same in in the in the main window, it will it will tell you which smooths will require an upgrade and which will sorry a reboot and which will not. Ok, so actually.52:09Let's like all of them, ok? So for the moment on these ones, there is NO overlap, right? So we can apply all of them. This is a very big image, ok? Now, what does it do in here?52:28With golden ISO, what you do is for a specific type of device, you define a standard for the image that it should be running. And that image can be the base release, right? In this case is 2542 or it can.52:44Maybe the base release plus a specific smooths combined, right? And once you define this.53:04Oh, let me see. I'm not sure if I should define it. Once you define this, what it will do, it will crawl the inventory of that specific time and it will tell you which devices are not compliant, right? So this is like a compliance capability. It's part of the compliance capability. I'm not gonna.53:14I'm not gonna run them, but that is basically what, then you will be able to see in the inventory, right? So you can see in here like the impact, but you will be able to see which devices are not.53:33Compliant with the minimum security, you know, fixes that you want to have in your network for that specific device. Now, this is helping you in two ways. One is visibility, of course, but then 2nd one is it will narrow down your entire inventory to the right devices that.53:48You need to do an upgrade for.54:08Okay, so it's an easier way to track, the way the state of your specific network. And this next to the golden config are two ways to kind of stay on top of, you know, having a standardized configuration and a standardized image for, for your.54:10For a device or for a specific category of of devices.54:30Okay, ok, so we already talked about the conformance ok and then I hope that was that was clear what we're gonna do now is, yeah, let's finish with this. Let's.54:34Let's talk about the golden config, right? So let me go back here go here Okay.54:55So again, what is building config? Its focus is to make sure again to have like a standardized configurations across specific devices and be aware of if there are any deviations deviations for that, right? In.55:12In the golden config itself, you can.55:32It's using ginger team templates, but you can use the style of different vendors, right? You can use, C style or g style which means Cisco style, a juniper style, we can use XML if you're comfortable with that or just jason. And this.55:37It's based on NSO, so basically what it happens is workflow automation, has a function inside which will just.55:57Pulling those capabilities directly from NSO and make them available in the interface in the interface in the UI for you. Okay, so this is based on NSO. You will not find details, specific details into the documentation, either CNCO workflow.56:07Information or, you know, crossword workflow manager on how to configure these devices. You, you need to go to the NSO documentation and in the NSO documentation you can see what you need to take into account to be able to create a template in this styles in here.56:26Okay. So that's important to keep in mind, because it can get confusing or discouraging that you know the documentation is not doing what it's supposed to do, ok? Ok, it goes to the NSO.56:44And as I mentioned its goal is to do is to do audits. So let's go and have a quick look. So in the golden config, we already have one in here. I'm not gonna be able to run because it goes on the same device that it's upgrading right now, but I'm gonna walk you through.57:02Do what it does?57:22So basically in here is we have two sections, right? So we have the templates and then we have the global variables. In the global variables, you basically define so let's say if we go, e.g., this is interface description.57:24You just define capabilities and you you define values from the system itself from CWM that you want to be able to address inside the template. So basically what to track in a way.57:43Okay, so if I put out in here we're gonna give it a name and then you just put the name of the of the value. I can put that in a string or in a json, in a JSON payload. Then when you go into the templates, you can reuse those values, right? So if I open this one, we can see.58:03That it's using already has the values that we've created globally and we can also create, if I go into this, we can see the two values in here. We can also add values if we want right in here if needed or we can modify them at the template.58:23Eight level.58:43Okay, then we can select the specific devices that we want to track, and then you know this would be the the job outputs. We have the description, the configuration type, so this is what I mentioned.58:45So native C style G style, right? So this is the way it's going to take the template and transform it or use it or the communication that it's going to be used between golden config to do you know the the checked audit and that specific.59:03Device Juniper has its own ways to interact with their devices, you know, Cisco has its own ways to interact with their devices. The config type in here helps make sure that we keep those, you know, appropriate. In this case it's gonna be just for for Cisco. You know, the software type right now it's iOS XR and XC.59:23And then we can select the specific product series. So in this case, you know, we gonna, this template is just checking for NCS 55 hundreds out of our inventory. Now what it will do.59:43It will do you can select if you want the template to already apply and start crawling the inventory and see if, you know, if there are any differences or deviations or you can, you know, just create it and run it whenever, whenever you want.59:57You can actually try to do a dry run, we can see that it's detecting, you know, all the devices that are right now in the, in the inventory.01:00:17Okay, just checking for this. Let's select so let's select on device let's just say dry run.01:00:27And this is the dry run result. Okay, ok, so the template it's working, right? It's doing its job. This is what the dry run it helps you. Now the the information you will see it in.01:00:43In the config, it should be let me see, you will run it, ok? So in this case is NCS 5500.01:01:03Okay, let's select all of them, the next, we select the template, select next it will test to see if you know there's a loopback interface configured. We select the mop, which is the built in one for Cisco.01:01:22Okay, the next we say test ok we leave it at standard again we can.01:01:44We can schedule it, right? Exactly like we had a look at for freight upgrade ok actually let's run it. Okay.01:02:03So it's running. Let's have a look. Okay, so it's still going on, we will see the results, it's gonna take a while for this one to run as well. Meantime let's go back to fleet upgrade, let's see.01:02:19The where are we? So it's finished with the distribution, right? So the image was uploaded and now it's in the activation state.01:02:39Now we have 24 min in. So in about 20 min it should be, it should be finished. Okay, let it run, let's go back to, yeah, the jobs.01:02:48Okay, so this one is ok good so let it run. So this is golden config, right? You set your variables, what do you want to check, then you create the template and you select on which devices.01:03:06Do you want to run this? And then you, you run the template against your inventory.01:03:26Okay, let's go back and this was golden config and then we have device migration and again this one I'm just gonna like I already mentioned what is its proper purpose.01:03:34But just to kind of go over it again.01:03:53This is for the situation where you do a replacement or like for like, where you want to be able to move the configuration to do a new device but keep track of what's going on around and that can be put inside the, a specific workflow that can be captured inside the specific workflow.01:03:57This, does not have, like I mentioned, it does not have a step by step guide, you know, for the device migration. And it's not something I mean it needs its own session because.01:04:17Basically to be able to, to demonstrate this, we have to build like a full lab for it, ok? With a bunch of devices where we replace one with the other and then we do the checks around. I think there is like a recording of this that maybe we could include.01:04:33Or shared publicly so you can see how this works. It is, but yeah, I cannot I cannot show it in here live especially not you know because this is one lab and we're already running two two jobs. So I don't wanna piece off the demo guards.01:04:53Oh, come on, go back. Okay, I don't want to piece off the demo guts you know and just let it finished with this too and hopefully both will be successful so we can see some of the results.01:05:13Okay, so while that is still running, let's run another slider just to see which of the solutions are actually interesting to you. And that's gonna give me some time to, you know, take a zip.01:05:33Cause I'm losing my voice How much time do we have? We have 20 min left, right? From the session.01:05:49Okay. So I think we are we are you know on time it should finish and we should be able to see the results David or Georgia, anything you guys wanna add?01:06:06Okay, at the moment, NO, I see that there are two questions. There were two questions in the chat. If you would like to, to go again, they were responded already, but if you want to comment something on it, that would be also good.01:06:26Yeah, so that that is a feedback. So Christy that is a feedback that we we gave to the business unit to consider enabling the possibility to upgrade modules independently inside CNC.01:06:55It is being considered it's not there yet right now, so you will have to move to CNC seven two to to to get the capabilities from two one or to have a separate instance of CWM, but that would complicate a bit things.01:07:16You know, it will add another tool for you to take care of, when you already have capabilities inside the CNC. Yeah and when it comes to the migration again.01:07:33This is something that, it's not, I mean, you have to flow out of the box, but the actual procedure itself needs to be created, right? Depending on the use case, depending on the setup around that specific box, what do you want?01:07:54Check what do you wanna make sure that you you can check before you do the migration. Okay, so that's why it's not something that we can fit together with flip upgrade and golden config into.01:08:1480 min, it will need its own session, but do be aware of the fact that it needs, it needs customization, right? And we're gonna look at the workflow right now just to see what does that mean, by creating a very simple workflow.01:08:30Yeah ok Julie, that's an interesting question. Yeah, maybe we.01:08:48You know, we take it at the end I'll let the guys reply for LLM assistant processes. There are two or three sessions at Cisco live, delivered by where he shows.01:09:05Use how he is using.01:09:25Oh, IDs, so visual studio, visual code yeah visual code I think and llmiss to create workflows but also to run them.01:09:31Directly from an agent by integrating with an agent. CWM itself has a, has a.01:09:50An MCP as, as well that you can play with and I mean the the plan is to go and add more of AI capabilities across the portfolio from a Cisco perspective, right? So stay tuned on that maybe towards the end of the.01:09:59Under year or beginning of next year, there will be there will be an announcement around the AEI, the AI fact.01:10:18But there are two or three sessions that were delivered Yes. Both at Cisco live, Las Vegas but I think they were delivered on Cisco Live Amsterdam, but just just look at the the recordings over there. Very interesting sessions and there are a lot of learnings.01:10:26The advice sharing in there on how to optimize and make it as deterministic as possible.01:10:46Also here last one I would like to add for the NSO part, if you are talking more about NSO, because I see that you're mentioning some nets, JD here, the next next quarter meaning in two months around will be an NSO session based on the MCP, the new MCP adaptive.01:10:52That has been released, right? So that is also a very good entry point if you want to start exploring about different I will say LLM assisted processes because you will be able to connect with different AI clients that you want and interact with this kind of tool. So, that would be interesting.01:11:12Think we will also share the registration link once available, so keep I will I can take your your contact from here and if if it's ready I can send to you this registration link if you are interested in that kind of topic about the MCP and into NSO, right?01:11:32Yeah. Thank you David. Yeah, so thank you everyone for voting. I just realized that we have a golden config instead of golden config, so thank you for being understanding. I see that a lot of people are interested in golden config and then mixed between.01:11:52Complete upgrade and device migration, as well as custom solutions. So that's good. It looks like there's interest for all of them. When it comes to custom solutions.01:12:12So this is where it's important to understand the smallest component, which is the workflow itself, ok? And basically the workflow is like a logical suite of steps that the worker will execute.01:12:22And in those steps you define exactly what the worker needs to do, ok? Prior to 2.1, this was being you would be able only to do it in code. You will have the representation over here, but you will not get what.01:12:42What it's showing right now, like the toolbox and be able to drag and drop and, you know, facilitate the creation of these of these workflows.01:13:01Now, I'm not gonna let this run completely because let's try to build one of ourselves and what we're gonna do is just set up a host name.01:13:15Okay, so let me just real quick. I have a smaller cheat sheet in here that I need to open. There we go. Okay.01:13:29Okay. Right, so what this small workflow would do is just set the host name on a specific router, ok? And this is very simple, but, it shows how you can.01:13:45Customized right? At the end, sometimes you just need simple tweaks, basic actions, basic procedures that you want to start with and capture within, you know, within.01:14:05The workflow automation module or CWM and probably that's why you've mentioned with the customized workflows, right? For those that voted for that. Then let's have a quick look. So what we're gonna do is we're gonna create two stages set host name and get host name. The 1st.01:14:19This one will change the host name on a specific device, in our case it's gonna be our guineapig, the ASR 1001, and then it's gonna go and get the host name and verify it, right? And if those two match then, then it's gonna be a successful, a successful workflow.01:14:39What we need in order to do that is we're gonna use restconf on that device so Restconf is enabled, and when we need the data path, right? That is being exposed by the server that is running on the on the device itself, which is built in with.01:15:00Into iOS, ISXC in this case. So we need a path to call the module that is in charge of getting or setting the the host name. We have to tell it how to communicate with it, right? So what data should accept back?01:15:19What type of data should send, right? In this case is application and we gonna use young data model with Jason for the configuration, and we're gonna use a patch so we have get put to delete in this case we're gonna use patch because we have something that's already config.01:15:39Figure we want to change it. And in terms of resources.01:15:59We're gonna use a pre built resource specifically that I already showed for the ASR 1001, and then or if you want to go for multiple devices, you know, again, you can go and use NSO. Now this is important. There are multiple specifications of serverless workflow design language.01:16:06Is something that is a standard, right? It's heavily used in the cloud world, and it's public, it's not something that it's built by Cisco, right? And it has multiple specs right now I think they are at spec 1.11 .2.01:16:25Inside.01:16:45Workflow automation, we are using a spec 0.8, and that's important because you know the different specs need to do different things. There are some changes so it's good to be aware of if you try to build something or you want to go to the documentation and try to.01:16:48Understand you know, the functions, the activities, the the way it works, this is what you should be looking for. So 0.8.01:17:08Okay, so, let's go and try to, to, to create it. So I I see that golden config finished. Okay, so we can see that all of them are conformant, right? So all of them have that loopback.01:17:19Active, right? So they are conformant with our state of the configuration. Now, again, this is gonna show up into the inventory as well and it's gonna run, you can come configure it to run periodically, right? And make sure that you know your devices stay up to date. Let's.01:17:39Let's look at the other one as well. Let's see where it is.01:17:58There we go. So we finished the activate. Okay, let's verify the version. We see the commit and now it's doing the post checks, right? Not health.01:18:03Sanity checks. Okay, so let it continue. It should take about four or 5 min maximum, so it should be finished by the end. Let's now go and quickly create a workflow.01:18:22So now we're gonna use the things that we already defined in workflow administration, right? Those templates. You have two ways to do it. So e.g., if you have a workflow and you want to export them and keep them in a repository, you can always import them back, right? We have the import function in here.01:18:35If you want to create a new workflow, then we just going to create and that's gonna open for us the designer. In the designer you have a dummy start up sequence, ok? And you have two sections, one on the right, which is the workflow properties.01:18:55And one on the left, which is the toolbox, ok? You can see this if you are advanced and comfortable with the several specifications, you can go and create this directly in code. The, this is an ID, right?01:19:13So an integrated developer environment that actually has linting, so basically it's gonna check the syntax, the sequencing errors, the formatting way better than if you do the same e.g. in code without applying.01:19:34And visual studio code without applying, you know, specific packs or add ons. This is already built in. And you will see that after each step it will require you to validate and the validation is gonna basically use the built in capabilities in here. And you can also have an option where you can split, where you see.01:19:54Your, what is it? Let me click here, there you go. Where you can see you know the the graphical version of the workflow, but you can see also the code. And this will actually, you know, navigate you through the different sections of the code. So you can see begin, it's gonna take you to that specific state. Now, inside the.01:20:14Workflow, I mean, for those that are you know comfortable with coding or have some basics of coding, you know, you've probably heard about functions. So in here they are called states. And this states can have different they can view of different types. And I'm just gonna switch.01:20:34To graph because that way I have more real estate and in those states, right? We have multiple types of states in here. So, we can.01:20:54Have an operation, which is what we have in here. You can see this is operation, right? We can have a thread like a thread to run things in parallel, right? So it will bifurcate our logic. We can have loops, which is four.01:21:08Each, we can have a switch which is if then, right? So it's conditions. And this probably will be the ones that you use the most. Besides that we can have a callback, which is gonna go towards a chat function, and then the events. The events like I've mentioned are those that we use to inter.01:21:28Interact with external systems or tools, ok? Or even to call again another workflow that we have already created. So what I'm gonna do is I'm gonna add a second operation in here. So I'm gonna rename this one.01:21:48And this is gonna be called set host name, ok? We have, so we can choose if we want to run this in parallel or sequential, default is sequential, so we can leave it like this.01:22:05It will automatically select the next step, you know, the connectivity is done automatic in here. So if I go oh sorry what I do I didn't save. Let me finish this. So set host name, ok.01:22:23Okay let's just say save. And then we go to the next one and we call this get host name, ok?01:22:41And the rest goes and stage like this. You can see like the end will be true and automatically for you, you know, the name for the next stage will be auto updated in here, ok? So now if we click.01:22:54On the background, on the canvas, we get to have access to the properties of this specific workflow, right? So we need to demo to name this demo host name.01:23:10Workflow. Okay, we give it a name. This is the versioning, so you can choose, it is encouraged to use a three digit versioning system. But again, for this workflow, you can have a version 1.1 or two zero.01:23:290101 where you add, you know, other steps in it and that way you can use them for different you know for for different purposes. E.g., you want to.01:23:46Check if the device is available 1st before you start, you know, going directly for the host name. You can tag it, so I'm gonna just tag it AI so I can easily search it and you can organize it as well. So we can call this demo AI and/and what it will do, it will do a folder like structure.01:23:58Sure, that will make it much more easy to, to navigate. Okay, let's save this. The other things that we can do is we can connect the form, right? So we haven't looked at forms, but I have one it's already created.01:24:17And this is basically gonna provide like a form where I need to input what host name do I want this to be changed to? Then we can check and mention when it should time out, you know, David from the from the defaults, how many.01:24:33Many times it should retry.01:24:53If there is an error or you can define a specific error that will get if you want to make it more, you know, intelligible you can define your own error in here and that will be captured in the audit logs which will make it simpler, you know, to understand where this is coming from and you know maybe personal.01:24:56To the specific workflow.01:25:16Okay, so I'm gonna leave it like this save, and now you can see I cannot create this. If I want to create it as it is right now, I cannot because 1st I need to validate it, right? And what it will do is gonna go in the background and do the linking. So now we can see like our code keeps evolving. Okay, so we have the two actions in here.01:25:18Sorry, to two states.01:25:39Let's go back to the graph, and what we need is now to actually interact with the device. So we're gonna do a rest call. As you can see, you have already e.g. NSO directly, you have CLI, email, you know, depending databases, you can add different activities.01:25:42Isn't here. So in our case, we're gonna do a patch.01:26:01So we're gonna drop the activity in the box of the operation itself, and then we're gonna do a get, right, to get the host name. So in the case of patch, so we can give it a name.01:26:05Okay, let's see if that so it changes. You can say data and what we need in here, it's we need the path. So I'm gonna copy it in the interest of time. Then we.01:26:27The data that we're gonna send, so basically I'm gonna explain it in a second, but what we're gonna say in here is in the native module of restconf, you know, of the data model, use the module host name.01:26:47And then take the variable that comes through the form, it is represented in the form of.host name in this case, right? And send it as part of the command to change the host name, right? What we also need to tell it is.01:27:06We need to give it two things in here. One is how the data should be accepted and this is application/I think it's young data plus Json, and I'm just gonna copy this.01:27:26Do the same. This is another content type. So these are things that you usually configure for the header when you do a rest call, right? It's not something that is specific, you know, to this. This is something that you would use to do API calls, yeah.01:27:46The right?01:28:06Application young data post json. Okay, that's good. Now we need to select how do we connect to the device? And that's something that we already defined in the administration. So I'm just gonna look for my device. So here's our demo router, ok? And then we have to define.01:28:09Main.01:28:29Let's see how do we put the results? And the results we need to pass them to the state data. What does that mean? So this is how, you know, we store the information, the result right of this operation, like success, e.g..01:28:32Into a variable that gets passed to the next stage, ok? So this is the way you defined variables.01:28:50And you can call it, you know, different ways. Okay, we saved that. As you can see, it will automatically turn this into JSON, so we have the data, the path that it's gonna use to send that data and then the header it's gonna use to connect and communicate with the.01:28:57The endpoint, ok? So we're gonna do the same for the other, so let's just call it, get host name, ok, let's go into the data.01:29:17We need to give it actually let me put the headers because I already have them in copy. Okay, so accept oops, I don't have anything. Let's, let's take them one by one again. So let's put the past.01:29:35Yes.01:29:54Okay, and let's put the payload, ok, which is the data we're sending and then so I don't waste time typing. Let's put this in here.01:29:57We're gonna do the same here and call it content type ok do the same and.01:30:14I think for the data, we should be ok. Results. Let's put it in current host name. There you go. Save this again we have the Json automatically created.01:30:30Okay, so this is how we create a workflow from scratch, yeah. Now, let's run it. Okay, I cannot create it yet because I need to validate it. So what it will do, it will, you know.01:30:49Check, do the linking and check the structure. So e.g., I don't know if I misspelled this, it will immediately say, you know, there are some problems.01:31:07Yeah, state set host name in here. So we have to go in here and just say and must have either an end definition or a valid transition, right? So the transition part is the problem you can see it's it's gonna underline it. So, you know, for those that are at the beginning, this is gonna be helpful for those that are more advised, this is gonna be.01:31:21Be helpful as well. We always validate again and now we can create. Now we have our workflow created. If we go back to workflows, we can see the structure. So demo AI, I can see it in here and we can run it.01:31:41Okay, so before doing that, this is the router, which I believe got disconnected, but this is the host name it has right now. So we can call it a NO CP.01:32:01Twelve is our 1001 CWM, gonna run it and right now it's running. Okay, so we have some failures which we can go and have.01:32:18Look. Yeah, so it's probably something that I haven't properly configured maybe something that in the in the header usually that's why I make some mistakes. So what we can do is we can go back.01:32:37Come on, we can go back into the into each and change and do the changes where am I in here. Okay, so I see I'm disconnected from this one. Let's go and see our jobs.01:32:57And see at least if this one finished.01:33:17Okay, so we have data which is done post. I'm conscious we are over time, sorry about that, but just to show this. So you can see this is the final stage to post and.01:33:21What it did, right? So we did the state before, it did the state after, and then it created, you know, you can see the details from those specific commands, but it can also show you a diff in between the two, what was added, right? So in this case, this specific smooth was added, so 2221 at the end, right?01:33:39Before it was not there. Now it's misleading because it's in red. Yeah, I agree and we had a discussion around this, that, you know, it's a bit yeah if if it's something that theoretically it's marked as different, then.01:33:59There should be some different actions or notification or the ability to, to, to message those that are responsible. And that is something that can be built inside inside the the workflow itself. But the goal here is just for visualization purpose of what changed and quick.01:34:19We understand like yeah, the upgrade happened. I didn't have this move before I have it now. It's applied, my device is up and running.01:34:39Okay, I can see the interfaces again and nothing changed on the interfaces, you know, those that are down or down, ok? And I can see in here what is this one? Oh yeah, it's just like the the version.01:34:48The uptime and so on. Okay, so this is upgrade. For the other one, unfortunately they didn't run properly, but you know I did run it yesterday and it worked with NO problems. So we can do the troubleshooting, we don't have the time to.01:35:05Do it right now. In general, usually what I make mistakes it's in the header, so application, you know, young modeling and so usually that's where the problem is. But that's the way you customize. So you create a small workflow that one turns into action and you can add it into your.01:35:25Method of procedures. So that workflow we can turn it into an action and make it actually part of it upgrade as a check, right? It can be added to that or to call them config or to a customized application. Yeah, that's the way you add further checks, right? That make you make you comfortable.01:35:45Okay, so, this is only detailing the, you know, the demo. That's why those were backup slides. Just before we finish, just to recap.01:36:05It's one engine you can install consume it in two ways inside CNC as a standalone. Everything is the same in between the two, right? The advantage in CNC is that the inventory is built by CNC with CWM, you have to do that manually or through NSO.01:36:21Integration. The credentials, they don't go into the workflow, you have reusable modules that you can use inside the workflow for like the adapters, like the again the the secrets, and that makes it much more flexible and safe.01:36:41And for the golden config, you know, validation and also for the workflows, you know, you have the linting and the capabilities inside the code to be able to validate, but still, you know, you need to do your own testing and.01:37:00Just start with something simple, I would say. I mean start with the fit upgrade, play with it, start with the golden config, play with it with one virtual device and and see how it works, and when it comes to building your one flow, workflow, like take the most basic repeat.01:37:20Action or small set of actions that.01:37:40You do on a daily basis or you already have captured into an operational flow and try to port it into into a workflow by leveraging the workflow designer and just see how it goes. Next session is gonna be in a week from now, same time building workflow.01:37:44With David, and I just say thank you for sticking with me. I'm sorry we went over time but you know, I really wanted to show that the fit upgrade actually succeeded and I hope the session was, was useful.01:38:04And after we close the session, there will also be a survey. So, feel free to provide feedback for improvements or any other topics that you would like to see the session dedicated dedicated for.01:38:23Well, thank you very much and I wish you a great day.01:38:40