cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
81
Views
0
Helpful
3
Replies
Cisco Employee

Is there a way to re-deploy several services in a single transaction?

I'm thinking here of changes in topology. Often these affect many services but in the end they result in changes on just a few devices.

If I call the re-deploy action in a loop I will have many transactions, and especially with cli NEDs it could take a long time. So a single transaction would be nice. I remember reading somewhere there was a way to do this, but searched through docs and could not find.

Stefano

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Re: Is there a way to re-deploy several services in a single transaction?

I saw there is a 'touch' action.

So I didi

request <service1> touch

request <service2> touch

commit dry-run  | debug template

and I could see it was running through the templates of both services

3 REPLIES 3
Cisco Employee

Re: Is there a way to re-deploy several services in a single transaction?

In the NSO CLI, there was an option to pass wildcard (*) when doing re-deploy for all instances of a service type. I'm wondering how that is implemented. If it just iterates over the service instance list or does something smart.

Beginner

Re: Is there a way to re-deploy several services in a single transaction?

With (*) It will iterate through all service instances and commit them one by one, you can check that by having two open NSO CLI's, if you issue a re-deploy in one, you'll see how many commits were issued in the other window. At least that was the case when I did the reconcile command, but i think that behind the scenes it still does the same re-deploy action.

Not sure yet how would you put this into one transaction though.

Highlighted
Cisco Employee

Re: Is there a way to re-deploy several services in a single transaction?

I saw there is a 'touch' action.

So I didi

request <service1> touch

request <service2> touch

commit dry-run  | debug template

and I could see it was running through the templates of both services