[SFC-185] Update GUI after deprecating nsh-aware in SF and other changes in model Created: 16/Jan/17  Updated: 03/Feb/17  Resolved: 03/Feb/17

Status: Resolved
Project: sfc
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Santiago Abascal Assignee: Santiago Abascal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 7554

 Description   

After the following commits, GUI should be updated:

1) https://git.opendaylight.org/gerrit/#/c/49687/
Removing deprecated SF fields - The SF fields nsh-aware and request-reclassification were deprecated in Beryllium. The fields were added to the SF-type, so use those instead.

In GUI (http://localhost:8181/index.html#/sfc/servicefunction) we can still see a field "NSH aware", but it's empty. This field should be removed, as nsh-aware is no longer an attribute of a Service Function, or at least updated with the nsh-aware field of the SF type this SF belongs to.

2) https://git.opendaylight.org/gerrit/#/c/49546/
Deprecating the SFC and RSP symmetric flags - Chain symmetry is now a function of the SF-type bidirectionality flag - The SFP symmetry flag, if present, will override the SF-type bidirectionality flag

In GUI (http://localhost:8181/index.html#/sfc/servicepath) there is a check box for "Symmetric path" which doesn't show the resulting symmetric feature of the path. That is, in case the SF type of one SF in the chain is bidirectional and the symmetric field in SFP is not set, this check box appears unchecked, which is confusing, because the path is actually symmetric.
An easy solution could be renaming this check box for example as "Force symmetric path", to reflect just the meaning of the symmetric field in SFP, not the resulting symmetric feature of the path.



 Comments   
Comment by Santiago Abascal [ 20/Jan/17 ]

https://git.opendaylight.org/gerrit/#/c/50552/

Generated at Wed Feb 07 20:38:51 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.