On 03/22/2017 04:36 PM, Feng Pan 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.
The dpdk plugin build process precipitated major headaches working for
downstream packaging for Centos as well. I had a patch ready to submit
for building from a dist tarball as a step toward building from a source
rpm but that can't be used now. The main problem is vpp can no longer
build from a isolated tarball without git. Installing the development
rpm as part of downstream installation is not an option either. The
build process does not support dependency on an external rpm yet such as
that which is built in rpm_dpdk project. I am thinking out load here but
the best option for achieving packaging for 17.04 is to build dpdk from
the tarball, bypass the dpdk rpm and include the upstream dpdk tarball
in the srpm. Hopefully we can get a better solution figured out by next
release over 17.0x that will work with the dpdk plugin concept.
Thanks
Feng
On Wed, Mar 22, 2017 at 2:46 PM, Ed Warnicke <hagb...@gmail.com
<mailto: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 <mailto: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>
[mailto: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 <mailto: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 <mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev
<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
--
*Thomas F Herbert*
SDN Group
Office of Technology
*Red Hat*
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
