Just to confirm.

Are all these patches +2 and merged?

@Tim, do we want to include such a build right now? should we wait until
the code is merged?

On Wed, Jul 27, 2016 at 6:35 PM, Tim Rozet <tro...@redhat.com> wrote:

> Thanks Brady.  I am going up update Apex SFC deployment to use this ODL
> version.  We recently added Tacker to our build process, so whenever we get
> fixes into SFC_colorado branch, they will automatically be picked up and
> included in the build.
>
>
> Tim Rozet
> Red Hat SDN Team
>
> ----- Original Message -----
> From: "Brady Allen Johnson" <brady.allen.john...@ericsson.com>
> To: sfc-...@lists.opendaylight.org, "OPNFV Tech" <
> opnfv-tech-discuss@lists.opnfv.org>
> Sent: Wednesday, July 27, 2016 11:14:52 AM
> Subject: [opnfv-tech-discuss] [SFC] A working ODL Boron distro (0.5.9) for
> testing with OVS 2.5.90 NSH
>
>
> We finally have a working ODL Boron distro for testing with the OVS 2.5.90
> NSH Yi Yang patch in OPNFV.
>
> You can get the distro here:
> https://drive.google.com/open?id=0B20dtomeEJsVc0tVVUdweG1IOG8
>
> I have set the version in the tarball name to 0.5.9, but when untarred,
> you'll see that the created directory is still 0.5.0. The 0.5.9 version is
> just something I came up with to be able to distinguish the different
> tarballs.
>
> Here is a list of issues we ran into while testing that should help:
>
>
>
>     * Classifier resubmit vs outport
>
>
>         * There is a bug in the Brahmaputra version of Tacker whereby it
> creates the classifier flow with an output, when it should resubmit to the
> SFC tables.
>         * We manually update this flow for now to get around this problem
>         * This problem existed before the OVS 2.5.90 changes
>     * Netvirt karaf features
>
>         * Any karaf features with the text "netvirt" in them should NOT be
> used, they will cause instabilities
>         * Only these Netvirt karaf features are needed:
>
>
>             * odl-ovsdb-sfc
>             * odl-ovsdb-sfc-rest
>     * SFC karaf feature rename and others not used in OPNFV (sb-rest, ui,
> netconf)
>
>         * The odl-sfcofl2 karaf feature was renamed to
> odl-sfc-openflow-renderer
>         * Only these SFC karaf features are needed:
>
>
>             * odl-sfc-model
>             * odl-sfc-provider
>             * odl-sfc-provider-rest
>             * odl-sfc-ovs
>             * odl-sfc-openflow-renderer
>     * Blocked port on Compute node
>
>         * We had a problem whereby the Fuel installer blocks all ports in
> the IP tables on the compute node and each needed port has to be manually
> "opened"
>         * If packets appear to not be entering the vxlan-gpe port, then
> its probably because they are being dropped by ip tables
>     * vxlan_tool.py update
>
>         * The previous version of the vxlan_tool.py used on the SF
> vxlan-gpe only supported vxlan-gpe + NSH + orig packet
>         * The latest Yi Yang OVS patches use vxlan-gpe + Eth + NSH + orig
> packet, so the tool needs to be updated to support this
>
>
> Here are the ODL patches in this distro:
> (They have all been rebased to master/boron today)
>
>
>     * Openflowplugin
>
>
>         * https://git.opendaylight.org/gerrit/37937
>     * SFC
>
>         * https://git.opendaylight.org/gerrit/37944
>     * Netvirt:
>
>         * https://git.opendaylight.org/gerrit/40942
>     * GBP: (We havent tested nor rebased this one yet)
>
>         * https://git.opendaylight.org/gerrit/40945
>
> Hopefully, tomorrow we'll formalize the final details to get these patches
> merged into ODL.
>
> Regards,
>
> Brady
>
>
> _______________________________________________
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> _______________________________________________
> sfc-dev mailing list
> sfc-...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/sfc-dev
>
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to