5 Setup the FD.io Repository - Centos 7
6 =====================================
11 Before starting the repository setup, it is a good idea to first update and upgrade
12 the OS; run the following commands to update the OS and get some packages.
14 .. code-block:: console
17 $ sudo yum install pygpgme yum-utils
20 Package Cloud Repository
21 ^^^^^^^^^^^^^^^^^^^^^^^^
23 Build artifacts are also posted to a packagecloud.io Repository. This includes
24 official point releases. To use any of these build artifacts, create a file
25 *'/etc/yum.repos.d/fdio-release.repo'* with the content that points to the
26 version needed. Below are some common examples of the content needed:
32 To allow *'yum'* access to the official VPP releases, create the file
33 *'/etc/yum.repos.d/fdio-release.repo'* with the following content.
35 .. code-block:: console
37 $ cat /etc/yum.repos.d/fdio-release.repo
40 baseurl=https://packagecloud.io/fdio/release/el/7/$basearch
44 gpgkey=https://packagecloud.io/fdio/release/gpgkey
46 sslcacert=/etc/pki/tls/certs/ca-bundle.crt
50 name=fdio_release-source
51 baseurl=https://packagecloud.io/fdio/release/el/7/SRPMS
55 gpgkey=https://packagecloud.io/fdio/release/gpgkey
57 sslcacert=/etc/pki/tls/certs/ca-bundle.crt
60 Update your local yum cache.
62 .. code-block:: console
65 $ sudo yum -q makecache -y --disablerepo='*' --enablerepo='fdio_release'
67 The *'yum install vpp'* command will install the most recent release. To
68 install older releases, run the following command to get the list of releases
71 .. code-block:: console
73 $ sudo yum --showduplicates list vpp* | expand
78 To allow *yum* access to the nightly builds from the VPP master branch, create
79 the file *'/etc/yum.repos.d/fdio-release.repo'* with the following content.
81 .. code-block:: console
83 $ cat /etc/yum.repos.d/fdio-release.repo
86 baseurl=https://packagecloud.io/fdio/master/el/7/$basearch
90 gpgkey=https://packagecloud.io/fdio/master/gpgkey
92 sslcacert=/etc/pki/tls/certs/ca-bundle.crt
96 name=fdio_master-source
97 baseurl=https://packagecloud.io/fdio/master/el/7/SRPMS
101 gpgkey=https://packagecloud.io/fdio/master/gpgkey
103 sslcacert=/etc/pki/tls/certs/ca-bundle.crt
106 Update your local yum cache.
108 .. code-block:: console
111 $ sudo yum -q makecache -y --disablerepo='*' --enablerepo='fdio_master'
113 The *'yum install vpp'* command will install the most recent build on the
114 branch. Run the following command to get the list of images produce by the
117 .. code-block:: console
120 $ sudo yum --showduplicates list vpp* | expand
125 To install the VPP packet engine, run the following command:
127 .. code-block:: console
129 $ sudo yum install vpp
131 The *vpp* RPM depends on the *vpp-lib* and *vpp-selinux-policy*
132 RPMs, so they will be installed as well.
136 The *vpp-selinux-policy* will not enable SELinux on the system. It
137 will install a Custom VPP SELinux policy that will be used if SELinux is
140 There are additional packages that are optional. These packages can be
141 combined with the command above and installed all at once, or installed as
144 .. code-block:: console
146 $ sudo yum install vpp-plugins vpp-devel vpp-api-python vpp-api-lua vpp-api-java vpp-debuginfo vpp-devel libvpp0
151 Once VPP is installed on the system, to run VPP as a systemd service on CentOS,
152 run the following command:
154 .. code-block:: console
156 $ sudo systemctl start vpp
158 Then to enable VPP to start on system reboot, run the following command:
160 .. code-block:: console
162 $ sudo systemctl enable vpp
164 Outside of running VPP as a systemd service, VPP can be started manually or
165 made to run within GDB for debugging. See :ref:`running` for more details and
166 ways to tailor VPP to a specific system.
169 Uninstall the VPP RPMs
170 ======================
172 To uninstall a VPP RPM, run the following command:
174 .. code-block:: console
176 $ sudo yum autoremove vpp*