Thanks for your quick responses. Sounds like I will have to go with option (1) for now, until I figure out how to do the split service or transform options that you mention as I am new to NSO/Yang. Unfortunately, from and end user perspecive it will add an extra text field to the model which serves no purpose other than to act as a key when the "switch-name interface-type interface-id" key would be much more elegant.
Our goal is to have NOC staff members use the new NSO 4.5 webui directly to add/remove/modify services (this service is specifically switch interface VLAN assignment - see the screenshot below). The new webui is fantastic and is SO CLOSE to being usable by NOC members directly rather than using NSO as a backend to another UI. The one hurdle we are having trouble overcoming is specifying a device interface as a string type is very limiting when presented directly to NOC staff. They understandably want a drop down of available interfaces to select from rather than a text box which requires them to identify an available interface using another tool and then type it manually into the NSO webui. Preferrably certain attributes would be displayed with each interface (such as interface description, VLAN assignment, or up/down status - similar to how the NSO cli displays interface descriptions using "show devices device <name> config ios:interface ?). All of this information is already in CDB and seemingly should be able to be referenced simply in a yang model. Any guidance is greatly appreciated. Thanks again for your help.
.png)
