cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
32
Views
0
Helpful
1
Replies
Highlighted
Cisco Employee

Recommended best practice to extend Service Package/Model

What is the recommended best practice to extend (change) a service package/service model which has been already used to deploy services and these services are operational in the network?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

1) Follow the YANG revisioning rules: Section 10.  Updating a Module in RFC 6020

2) Update the mapping templates/code

3) Reload packages

4) Redeploy services

This is actually a killer demo. I do this live for customers. Add a simple leaf to the model

Edit a template to include that new leaf and write something to the device, reload packages, redeploy services

As usual - the devil in the details. Sometimes, the NEDs need to be updated, maybe because we need additional features, maybe it turns out that one of the features we're using needs to be YANG redesigned. If the NED is stable we're probably good, if the device is yang/netconf we're probably good. Update of yang service model we can control our selves, whereas the NEDs are ... well more hidden. If a NED is updated hard, we probably want to combine that with a a sync-from on the devs, a redeploy on the services.

Might be pretty disruptive if the NED changes are bad.

View solution in original post

1 REPLY 1
Highlighted
Cisco Employee

1) Follow the YANG revisioning rules: Section 10.  Updating a Module in RFC 6020

2) Update the mapping templates/code

3) Reload packages

4) Redeploy services

This is actually a killer demo. I do this live for customers. Add a simple leaf to the model

Edit a template to include that new leaf and write something to the device, reload packages, redeploy services

As usual - the devil in the details. Sometimes, the NEDs need to be updated, maybe because we need additional features, maybe it turns out that one of the features we're using needs to be YANG redesigned. If the NED is stable we're probably good, if the device is yang/netconf we're probably good. Update of yang service model we can control our selves, whereas the NEDs are ... well more hidden. If a NED is updated hard, we probably want to combine that with a a sync-from on the devs, a redeploy on the services.

Might be pretty disruptive if the NED changes are bad.

View solution in original post

Content for Community-Ad
Cisco Community August2020 Spotlight Award Winners