Looping in the fdio-puppet folks and FDS folks as this will be germane to how they choose to configure/install vpp.
Ed On Fri, Mar 24, 2017 at 9:26 AM, Damjan Marion (damarion) < damar...@cisco.com> wrote: > > Dear Feng, > > We have VPP consumers which would like to use VPP in the containerized > environment without DPDK so dpdk needs to be separate package. > Regarding your particular problem, it should be fixed with > https://gerrit.fd.io/r/#/c/5837/ as Dave suggested. > > Thanks, > > Damjan > > On 22 Mar 2017, at 21:36, Feng Pan <f...@redhat.com> wrote: > > So this would suggest that VPP by default (that is, by doing 'yum install > vpp') will not have dpdk support, and vpp-plugins must also be installed to > add it, I would think dpdk plugin should be either packaged or installed > together with VPP by default, and can be disabled if desired. > > In any case, will deployment model stay this way? I'll need to make > changes to puppet module to include other packages if that's how it will be > going forward. Also, dpdk section should be commented out in the config > file so we can start VPP service using the default config. > > Thanks > Feng > > On Wed, Mar 22, 2017 at 2:46 PM, Ed Warnicke <hagb...@gmail.com> wrote: > >> Commenting out the dpdk stanza is a great workaround but we may want to >> look at bit more closely at the issue... as installing the vpp project >> should result in an out of the box runnable vpp. >> >> Ed >> >> On Wed, Mar 22, 2017 at 11:44 AM, Dave Barach (dbarach) < >> dbar...@cisco.com> wrote: >> >>> Simply remove the “dpdk” stanza from /etc/vpp/startup.conf if you want >>> to run vpp without the dpdk plugin. >>> >>> >>> >>> Thanks… Dave >>> >>> >>> >>> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] >>> *On Behalf Of *Feng Pan >>> *Sent:* Wednesday, March 22, 2017 1:47 PM >>> *To:* vpp-dev <vpp-dev@lists.fd.io> >>> *Subject:* [vpp-dev] vpp-plugins RPM dependency >>> >>> >>> >>> Hi All, >>> >>> >>> >>> With latest master builds of VPP (on Centos with rpm repo), it seems >>> like it's necessary to install vpp-plugins package for vpp to start, >>> without it, I get the following error when running vpp (with default config >>> file): >>> >>> >>> >>> vlib_plugin_early_init:360: plugin path /usr/lib/vpp_plugins >>> >>> vlib_call_all_config_functions: unknown input `dpdk ' >>> >>> >>> >>> Looking at the spec file, vpp package depends on vpp-lib only, so it >>> appears that we need to add vpp-plugins to the dependency list too. >>> However, it also looks like vpp-plugins depends on vpp package, so I'm >>> trying to figure out what the right dependency relationship is :) >>> >>> >>> >>> Thanks >>> >>> Feng >>> >>> _______________________________________________ >>> vpp-dev mailing list >>> vpp-dev@lists.fd.io >>> https://lists.fd.io/mailman/listinfo/vpp-dev >>> >> >> > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev > > >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev