[ICN-333] Investigate OpenNESS 20.03 Created: 16/Apr/20 Updated: 16/Jul/20 |
|
| Status: | In Progress |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | High |
| Reporter: | Chenjie Xu | Assignee: | Chenjie Xu |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | OpenNESS integration in ICN |
| Description |
|
OpenNESS team has released OpenNESS 20.03. Will investigate this 20.03 release to see what can be integrated with ICN R4. |
| Comments |
| Comment by Chenjie Xu [ 29/Apr/20 ] |
|
The email from Srini: ------------------------------------------ Hi Krishna,
Are both cUPF and dUPF are closed source?
Hi Chenjie,
Since any platform feature (dUPF is considered as platform feature for Edges) by ICN BP family, we can’t have closed source. Let us suspend this work in MICN BP. In another BP (private-5G ICN BP), dUPF is being developed (with VPP UPF as the base). Let it be part of that BP for now. We can take that to MICN BP at later time.
Thanks Srini |
| Comment by Chenjie Xu [ 29/Apr/20 ] |
|
OpenNESS UPF won’t be integrated as it’s close source. Need Srini to confirm whether to integrate OpenNESS AF&NEF or not. |