I added a kill-switch for the SFC dependency in NetVirt the last time
we ran into similar issues, so disabling SFC is straightforward:https://git.opendaylight.org/gerrit/c/netvirt/+/84369
On Thu, Sep 12, 2019 at 10:27:28PM -0700, JamO Luhrsen wrote:
> I think it's time to get SFC out of our managed projects list. It really
> only remained all this time because of netvirt's dependency on it.
> However, I don't know if we want to try to do this for Sodium, do we?
> Or is it already decoupled from netvirt?
> On 9/12/19 3:39 PM, Abhijit Kumbhare wrote:
> > Hi SFC team,
> > During the TSC meeting today we discussed this issue as well as SFC in
> > general. We decided to remove the SFC dependency and SFC tests from the
> > NetVirt project. However, I would like to ask a broader question. Given
> > that most of you are not full time on the project, do you folks want to
> > remove SFC from being a managed project from Sodium? In that case you
> > can turn it into a self managed project - and can be included if you
> > desire using the lightweight self managed process. Alternatively as a
> > self managed project you can also remove it from Sodium altogether. You
> > do not have to do the SRs if you are a self managed project, but if
> > support is unlikely to happen, then it will be cleaner to not have SFC
> > in the release in the first place.
> > In either case, in case you want to move SFC to self managed, we will
> > need to move fast as the release is already due. Please let us know
> > right away.
> > Thanks,
> > Abhijit