[GBP-185] Addition of chain in neutron mapping OS environment causes tunnel NPE Created: 12/Aug/15  Updated: 08/Sep/15  Resolved: 08/Sep/15

Status: Resolved
Project: groupbasedpolicy
Component/s: DSLMapping:Neutron
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Keith Burns Assignee: Igor Bartak
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 4128
Priority: High

 Comments   
Comment by Keith Burns [ 25/Aug/15 ]

1. Even though both tunnels are in datastore, Switch Manager for some reason isn't getting the VXLAN GPE tunnel added to its list of tunnels by type. I pushed a draft that addresses part of this. You will need to debug when the tunnels get created, added to datastore, and the corresponding notification that SwitchManager receives.

2. You can see this bug when you try and add the chain action to the neutron-mapper generated contract. To do this, its easier if you have the gbpsfc devenv up anyways, as you will need something for devstack to talk to anyway.

  • stack devstack
  • start controller
  • start gbpsfc demo – pick symetry
  • start script (step01.sh) in devstack
  • you should have two VMs in devstack, two tenants in datastore (devstack one and gbpsfc one)
  • gbpsfc one will have action-instance for chain. devstack will only have neutron allow.
  • test VMs can ping each other over normal allow action data path
  • copy the action-instance of chain into the tenant information for devstack.
  • paste the whole tenant information back (put to tenant) for both tenants.
  • now you can edit the tenant config offline (notepad, jsoneditoronline etc), and modify the contract between the EPGs to use the chain action instance instead of the allow action instance.
  • when you push this, you should see the flowmap update (ie table4, table 6) with NSP/NSI information
  • then you need to pass traffic through the classifier associated with the chain action.
      • note, I had issues with the wrong kernel.ko mod installed... if you get to the point you think you have correctly configured a chain with the above patch, ping me, but its a LOT of work just to get to this point.
Comment by Keith Burns [ 08/Sep/15 ]

Fixed. Publishing this gerrit: https://git.opendaylight.org/gerrit/#/c/25926/

Comment by Martin Sunal [ 08/Sep/15 ]

https://git.opendaylight.org/gerrit/#/c/25926/2
https://git.opendaylight.org/gerrit/#/c/26666/2

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