Release TeraFlowSDN 5.0

Lluis Gifre Renomrequested to merge
develop into master

Release Notes:

  • #19 (closed) : Enable gRPC reflection in Python-based services
  • #27 (closed) : Device reports CryptographyDeprecationWarning: Blowfish has been deprecated
  • #33 (closed) : Include method being retried
  • #74 (closed) : SmartNIC support for Morpheus
  • #117 (closed) : P4 SBI driver fixes to support in-band network telemetry
  • #118 (closed) : New P4 Service handler to support end-to-end services with In-band Network Telemetry
  • #139 (closed) : P4 driver does not correctly retrieve resources
  • #140 (closed) : Grafana settings lost when host ethernet interface goes down and back up
  • #163 (closed) : Implement CAMARA-based NBI connector
  • #191 (closed) : Implement Telemetry Backend Collector Emulated
  • #215 (closed) : Implement L3 VPN SBI driver compatible with IETF L3 Service Model
  • #216 (closed) : Implement integration test between E2E-IP-Optical SDN Controllers
  • #222 (closed) : Style fixes in SBI and P4 test
  • #223 (closed) : P4 resource keys with unique IDs
  • #224 (closed) : Add OpenFlow support through Ryu SDN controller
  • #225 (closed) : Pass P4 device endpoints through init settings
  • #226 (closed) : P4 test for INT, routing, and ACL dataplane setup
  • #227 (closed) : P4 fix handling of modify() vs. insert() entries
  • #228 (closed) : Parse P4 CloneSession entries from JSON
  • #230 (closed) : Fix websockets incompatible dependency versions
  • #231 (closed) : Merge Hackfest 5 in develop and related code fixes
  • #232 (closed) : Add ZTP server that provide a zero touch provisioning to whiteboxes
  • #233 (closed) : Fix CI/CD pipeline end-to-end tests not passing
  • #234 (closed) : Add wrappers to implement features related to NFV Orchestrator
  • #237 (closed) : Elaborate IETF Slice NBI to support adding/deleting new sdp, connection group, and match criteria
  • #238 (closed) : Required Service Handler to Support TFS Services that Manage IETF Slice and NCE Access Controllers in SBI
  • #239 (closed) : Driver to interact with NCE controller
  • #240 (closed) : Driver to interact with IETF Slice Compliant Controller
  • #241 (closed) : L3NM-NCE Service Handler
  • #242 (closed) : L3Slice-IETFSlice Service Handler
  • #243 (closed) : Elaboration of the service component to handler IETF Slice and NCE domains
  • #244 (closed) : Add missing device types in PathComp ComputeSubServices logic
  • #245 (closed) : Define fields to specify type of link
  • #246 (closed) : Implement methods to retrieve TopologyDetails in NBI
  • #247 (closed) : Analytics Module Enhancements
  • #249 (closed) : Telemetry Enhancement
  • #250 (closed) : CAMARA Demo Integration tests
  • #251 (closed) : Update NBI WebSocket endpoints to Flask-SocketIO and use gunicorn
  • #252 (closed) : Fixing visual presentation issues regarding the CAMARA demo
  • #266 (closed) : Update recommendations to use SocketIO on NBI and E2E Orch components
  • #268 (closed) : Prevent SBI pod crash when P4 driver reboot detects remnant switch without P4 binaries
  • #272 (closed) : New P4 Service handler for L3NM
  • #273 (closed) : New P4 Service handler to support Access Control Lists
  • #274 (closed) : Redundant Subservice Creation After Multi-Domain Service Update
  • #275 (closed) : New P4 Service handler for L2NM
  • #276 (closed) : Common library for all SD-Fabric P4 service handlers
  • #277 (closed) : SmartNIC support data model
  • #282 (closed) : ACL support in gNMI/OpenConfig SBI is required
  • #283 (closed) : PatchComp overwrites service configuration
  • #287 (closed) : ACLs applied on multiple endpoints of a device are not removed by deleting the ACL
  • #288 (closed) : QKD App component uses wrong database name
  • #289 (closed) : Fixes in P4 fabric-tna tests
  • #290 (closed) : Polish WebUI style and copyright line
  • #291 (closed) : Update copyright headers for R5
  • #297 (closed) : Resolve issue with common library and missing import
Edited by Lluis Gifre Renom

Merge request reports

.gitlab/issue_templates/bug.md

+3 −4
Changes for .gitlab/issue_templates/bug.md: 3 added lines, 4 removed lines.
Original line number Diff line number Diff line 
# Reporters



- name-of-proposer-1 (institution-of-proposer-1)

- name-of-proposer-2 (institution-of-proposer-2)

...



# Description



Describe the bug.

If needed, Attach logs and reports to your bug.

If needed, feel free to point external content as references (journal paper, Youtube video, etc.).
@@ -15,7 +13,6 @@ If needed, feel free to point external content as references (journal paper, You 
- MicroK8s (include version and add-ons):

- TeraFlowSDN (include release/branch-name/commit-id):





## TFS deployment settings

- list of components deployed

- particular configurations you applied
@@ -33,7 +30,9 @@ If needed, feel free to point external content as references (journal paper, You 
## Expected behaviour

- describe the expected behavior (if you know it)



# References

## Acknowledgements

This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.



# References

1. [Reference name](https://reference-url)

2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.

.gitlab/issue_templates/enhancement.md

+3 −4
Changes for .gitlab/issue_templates/enhancement.md: 3 added lines, 4 removed lines.
Original line number Diff line number Diff line 
# Proposers



- name-of-proposer-1 (institution-of-proposer-1)

- name-of-proposer-2 (institution-of-proposer-2)

...



# Description



Describe your proposal in ~1000 characters.

You can reference external content listed in section "References" as [Ref-1].



# Demo or definition of done



Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.

You can reference external content (example, demo paper) listed in section "References" as [Ref-2].



# References

## Acknowledgements

This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.



# References

1. [Reference name](https://reference-url)

2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.

.gitlab/issue_templates/new-feature-with-design.md

+3 −11
Changes for .gitlab/issue_templates/new-feature-with-design.md: 3 added lines, 11 removed lines.
Original line number Diff line number Diff line 
# Proposers



- name-of-proposer-1 (institution-of-proposer-1)

- name-of-proposer-2 (institution-of-proposer-2)

...



# Description



Describe your proposal in ~1000 characters.

You can reference external content listed in section "References" as [Ref-1].



# Demo or definition of done



Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.

You can reference external content (example, demo paper) listed in section "References" as [Ref-2].



# References

## Acknowledgements

This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.



# References

1. [Reference name](https://reference-url)

2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.



# Feature Design (for New-Features)



## Clarifications to Expected Behavior Changes



Existing component logic and workflows between components that need to be altered to realize this feature.

Remember to justify these changes.

...



## References



List of relevant references for this feature.

...



## Assumptions



Enumerate the assumptions for this feature, e.g., fix XXX is implemented and merged, specific configurations, specific

components deployed.

...



## Impacted Components



List of impacted components: Context, Device, Service, PathComp, Slice, Monitoring, ZTP, Policy, NBI, etc.

Just an enumeration, elaboration of impacts is done below.



## Component1 Impact



Describe impact (changes) on component1.

...



## Component2 Impact



Describe impact (changes) on component2.

...



## Testing



Describe test sets (unitary and integration) to be carried out.

This section can include/reference external experiments, demo papers, etc.

...

.gitlab/issue_templates/new-feature.md

+3 −4
Changes for .gitlab/issue_templates/new-feature.md: 3 added lines, 4 removed lines.
Original line number Diff line number Diff line 
# Proposers



- name-of-proposer-1 (institution-of-proposer-1)

- name-of-proposer-2 (institution-of-proposer-2)

...



# Description



Describe your proposal in ~1000 characters.

You can reference external content listed in section "References" as [Ref-1].



# Demo or definition of done



Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.

You can reference external content (example, demo paper) listed in section "References" as [Ref-2].



# References

## Acknowledgements

This work is funded by <FUNDING-ORGANISM> through the <CALL-NAME> <PROJECT-ACHRONYM> project with <PROJECT-ID/REFERENCE>.



# References

1. [Reference name](https://reference-url)

2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.

coverage/.coveragerc.template

+1 −1
Changes for coverage/.coveragerc.template: 1 added line, 1 removed line.
Original line number Diff line number Diff line 
# Copyright 2022-2024 ETSI SDG TeraFlowSDN (TFS) (https://tfs.etsi.org/)

# Copyright 2022-2025 ETSI SDG TeraFlowSDN (TFS) (https://tfs.etsi.org/)

#

# Licensed under the Apache License, Version 2.0 (the "License");

# you may not use this file except in compliance with the License.