-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DO-NOT-MERGE] Promote slice configuration to its own netcfg subject #459
base: main
Are you sure you want to change the base?
Conversation
We wil use netcfg for initialization
We wil use netcfg for initialization
Sytem is not a traffic class
It was hard to kkep track of the different app names used
Codecov Report
@@ Coverage Diff @@
## main #459 +/- ##
============================================
+ Coverage 66.95% 67.13% +0.17%
- Complexity 621 632 +11
============================================
Files 63 58 -5
Lines 4452 4442 -10
Branches 472 480 +8
============================================
+ Hits 2981 2982 +1
+ Misses 1235 1212 -23
- Partials 236 248 +12
Continue to review full report at Codecov.
|
Regarding Slicing API in the ONOS core - don't we have already a review from @Wailoks ? |
We agreed to put this on hold during the stand up on 1/24. Will revisit this once we need to support dynamic update / move slicing service to ONOS core. And to @pierventre 's comment - I believe you referred to this one https://gerrit.onosproject.org/c/onos/+/24932, but it has to be updated too since Carmelo introduced some API changes in this series. |
Yup - mine was just a reminder :) |
a6ebb69
to
fe32c4a
Compare
This PR is not functional and should not be merged.
We propose an alternative schema to the one introduced in #454 and #457. Instead of being nested inside an app config, slices get configured using their own netcfg event subject. The main benefit is that apps like
NetcfgSlicingProvider
can listen to events for individual slices, simplifying the diff update logic.Example netcfg:
Unfortunately, this approach doesn't work in its current form. For
SliceId
to be used as a subject class, it needs to be registered in the Kryo serializer of ONOS'sDistributedNetworkConfigStore
. We cannot make ONOS depend on fabric-tna. The right solution would be to moveSliceId
and other classes to the ONOS core.TODO:
SlicingService
API classes to ONOS core