Manuel/Babu,

I didnt see your emails on the OPNFV SFC lists. The OPNFV Tech Discuss list has 
way too many emails to keep up with. In the future, can you please put "[SFC]" 
in the subject so that your emails go to the OPNFV SFC list.

For starters, your statement about reg0=0x1 is based on using ODL Boron, and 
this will change in ODL Carbon. I mention this, because in Carbon it will be 
easier for the classifier to direct what to do with the packets at chain 
egress, like egressing them out of Openstack.

It is indeed a very valid use case for traffic to originate from outside of 
Openstack. Likewise for traffic destined to the internet, also a very valid use 
case. Probably the main reason we dont have anything setup for that now is for 
simplicity in our test cases, but its about time we look into doing this. 
Integrating L3VPN with SFC would certainly simplify this, but we should 
investigate how to do this without it.

Thanks,

Brady

-----Original Message-----
From: Manuel Buil <[email protected]<mailto:manuel%20buil%20%[email protected]%3e>>
To: [email protected] 
<[email protected]<mailto:%[email protected]%22%20%[email protected]%3e>>
Cc: Babu Kothandaraman 
<[email protected]<mailto:babu%20kothandaraman%20%[email protected]%3e>>
Subject: [sfc-dev] [Fwd: RE: [opnfv-tech-discuss] [fuel][plugins][odl] SFC 
agent for SFs/SFFs/Classifiers creation]
Date: Tue, 25 Apr 2017 15:34:46 +0200


Hi guys,

Babu has a very interesting use case (read below) that he posted in the
OPNFV-SFC mailing list. I think that the use case cannot be implemented
with ODL Boron becase of two problems:

1 - Right now only traffic which comes from local VMs where the
classifier is implemented is classified. The key here is the match
parameter reg0=0x1 which is only added to that local traffic. Because
of this, we cannot classify traffic coming from outside of OpenStack
towards a server VM.

2 - Imagine the traffic destination is not a server VM in openstack and
that traffic is just forced to go to openstack. It accesses SFC and
then must come back to the original destination, as far as I know, we
have no way to redirect the traffic to a destination which is outside
of openstack, right? Until the interation with L3VPN is not done, I
don't know how this could be done.

Do you agree or am I missing anything? Is any of these problems going
to be solved with ODL Carbon?

Thanks,
Manuel

_______________________________________________
sfc-dev mailing list
[email protected]<mailto:[email protected]>
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

Reply via email to