[SFC-223] Creating sfc flow classifier without --logical-source-port dosen't work Created: 02/Jul/18  Updated: 09/Jul/18

Status: Open
Project: sfc
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Medium
Reporter: Y Ananth Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

steps to reproduce:
1. create network
2. create three ports sf_port, source_port, dest_port
3. create three instances with ports.
4. create flowclassifier (without --logical-source-port option flow classifier doesn't work)
(openstack) sfc flow classifier create --ethertype IPv4 --source-ip-prefix 10.0.0.5/32 --destination-ip-prefix 10.0.0.6/32 --protocol tcp --destination-port 80:80 FC_1
5. create port pairs using
(openstack) sfc port pair create --ingress=sf_port --egress=sf_port PP1
6. create port pair group
(openstack) sfc port pair group create --port-pair PP1 PG1
7. create port chain
(openstack) sfc port chain create --port-pair-group PG1 --flow-classifier FC_1 PC1
8 check communication between source_vm and dest_vm (doesn't work)

note: create ports with security group allow all rules



 Comments   
Comment by Jaime Caamaño Ruiz [ 05/Jul/18 ]

logical-destination-port requires a logical-source-port. logical-destination-port is used for the reverse path of a symmetric chain for which a forward path has to exist as it is symmetric.

What is the expected behavior of using logical-destination-port without logical-source-port?

Comment by Y Ananth [ 05/Jul/18 ]

Yes, I understand it. But I think it should not allow to create without logical-source-port and should give error if we try to create it.

Comment by Jaime Caamaño Ruiz [ 06/Jul/18 ]

Yes, but that would be on openstack networking-sfc side of things. I am really curious to know how this scenario works when not integrating with ODL.

Comment by Jaime Caamaño Ruiz [ 09/Jul/18 ]

Removed incorrect reference to an unrelated bug.

Generated at Wed Feb 07 20:38:57 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.