Hi,
What is the preferred way of developing a cfs package in multivendor enviroment with regards to port names and numbering?
The solutions are:
- developing some abstract names of ports that are later translated to vendor specific names - adds cruft to the package but makes it independent of NEDs and device specific data. For example "ethernet 1/1" maps to "Ethernet 1/1" or "Ethernet 1" depending on the device.
- using 'case' statement in top level package, like pasted below.
In my case NSO will have a 3rd party GUI application. I want to make the cooperation with GUI developer as simple as possible. I would like to:
- avoid the situation where the GUI has to have some variable scenarios dependent on device type etc.
- minimize the impact of adding a additional device type in future
- have too many interactions between GUI and NSO to find details about the device
grouping access-trunk {
choice device-types {
case nexus {
when "/ncs:devices/ncs:device[ncs:name=current()/device]/ncs:capability[ncs:uri='http://tail-f.com/ned/cisco-nx']";
uses access-trunk-nexus;
}
case arista {
when "/ncs:devices/ncs:device[ncs:name=current()/device]/ncs:capability[ncs:uri='http://tail-f.com/ned/arista-dcs']";
uses access-trunk-arista;
}
}
}
thanks,
