Hi Srikanth,
I would try switching to Boron SR2 (0.5.2)
BR,
George
From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, March 03, 2017 9:33 AM
To: Paraskevopoulos Georgios ; Brady Allen Johnson
; opnfv-tech-disc...@lists.opnfv.org;
sfc-dev@lists.opendaylight.org
Subjec
Hi George,
I am using OPNFV Colorado 3.0.
Its ODL Boron 0.3.0, I think.
Regards,
Srikanth.
From: Paraskevopoulos Georgios [mailto:geo...@intracom-telecom.com]
Sent: Friday, March 03, 2017 12:45 PM
To: Brady Allen Johnson ;
opnfv-tech-disc...@lists.opnfv.org; Srikanth Lingala
; sfc-dev@lists.ope
Hi Srikanth,
Which ODL version are you using? We had some issues too in Colorado with
multicompute setups.
BR,
George
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Brady Allen
Johnson
Sent: Thursday, March 02, 2017 3:4
Adding sfc-dev.
Thanh
On Thu, Mar 2, 2017 at 10:12 PM, Jenkins wrote:
> Attention OpenDaylight-devs,
>
> Autorelease beryllium failed to build sfc-openflow-utils in build
> 164. Attached is a snippet of the error message related to the
> failure that we were able to automatically parse as well
I didn’t try this, so I haven’t any details, will opnfv sfc have such use case?
The below command can check if the packet is dropped or not
sudo ovs-appctl dpif/dump-flows br-int
From: sfc-dev-boun...@lists.opendaylight.org
[mailto:sfc-dev-boun...@lists.opendaylight.org] On Behalf Of Brady Al
Brady,
On which interface, you want me do tcpdump in the compute node.
As br-int is OVS port, we can’t see packets on that.
Regards,
Srikanth.
From: Brady Allen Johnson [mailto:brady.allen.john...@ericsson.com]
Sent: Thursday, March 02, 2017 9:18 PM
To: opnfv-tech-disc...@lists.opnfv.org; Srikant
Srikanth,
We experienced a similar problem lately in OPNFV SFC when using multiple
compute hosts. The situation was that the packets returning from an SF entered
the SFF on the XVLAN-GPE port, and then the packets need to go to an SFF on a
different compute host, and they do so on a normal VXLA
Devendra,
fyi, lithium and kilo are not supported anymore, but I don't think that is
the issue. linux bridge is handled by openstack neutron agents, the l3
agent I think. I would check if that configuration is correct.
Sam
On Thu, Mar 2, 2017 at 7:03 AM, Devendra Singh Rawat <
devendra_ra...@inf
Since this is more of an issue with OPNFV SFC than ODL SFC, I will add that
mail list.
Regards,
Brady
-Original Message-
From: Srikanth Lingala
mailto:srikanth%20lingala%20%3csrikanth.ling...@nxp.com%3e>>
To: sfc-dev@lists.opendaylight.org
mailto:%22sfc-...@lists.opendaylight.org%22%
Hi All,
We have integrated Openstack Kilo with ODL Lithium SR4.
After integration all networking works good (VM has IP, connectivity etc)
though we can't see any linux bridges getting created when an instance is
initiated. Isn't the linux bridges supposed to implement the openstack security
gro
PS: Sorry, If I am resending the mail to the sfc-dev mailing list. As I can't
find the mail in the mailing list, I am resending it.
Hi,
I am able to run SFC usecase successfully with single Compute Node.
Now, I am trying SFC usecase across multiple computes with Opendaylight,
Openstack and OVS w
SFC, offset 2
1. Please provide updates on any previously-incomplete items from prior
milestone readouts. N/A
2. Has your project achieved API freeze such that all externally accessible
Stable or Provisional APIs will not be modified after now? Yes.
(Link to gerrit search for patches modifyin
12 matches
Mail list logo
