c7f3139533
* First draft of Ubuntu 20.04 Vagrantfile and scripts to install 2021-Mar version of open source P4 development tools. * Add more tracing output of what files have been installed at each step * Don't do behavioral-model install_deps.sh before installing PI This is an experiment to see if the end result will be able to run tutorials basic exercise using Python3 only on an Ubuntu 20.04 system. Just before this commit, `vagrant up` resulted in a system that failed to run the basic exercise, because python3 failed to import google.grpc (if I recall correctly -- it may have been a different google.<something> Python3 module name). * Add missing patch file * Fix copy and paste mistake * Add missing patch file * Change how protobuf Python3 module files are installed * Correct a few desktop icon file names, and add clean.sh script * Enhance clean.sh script, and add README for manual steps in creating a VM * Changes to try to always use Python3, never Python2, in tutorials * Update README steps for preparing a VM * More additions to README on steps to create a single file VM image * Add empty-disk-block zeroing to clean.sh script * Also install PTF * Update versions of P4 dev tool source code to 2021-Apr-05 This includes a change to p4lang/PI that allows P4Runtime API clients to send the shortest byte sequences necessary to encode integer values, which I want for a PTF test that I have recently created. * Update README for 2021-Apr-05 version of VM image * Resolve Python 3 compatibility issues Most of the Python 2 to 3 code translation changes were automated with the 2to3 tool. Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org> * Update commit SHAs for 4 p4lang repos to latest as of 2021-May-04 * Update Ubuntu 20.04 README.md for how I created 2021-May-04 version of VM * mycontroller: Use Python 3 shebang line Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org> * Update Ubuntu 20.04 README.md for how I created 2021-Jun-01 version of VM * Update commit SHAs for 4 p4lang repos to latest as of 2021-Jul-07 * Update Ubuntu 20.04 README.md for how I created 2021-Jul-07 version of VM * Update commit SHAs for 4 p4lang repos to latest as of 2021-Aug-01 * Update Ubuntu 20.04 README.md for how I created 2021-Aug-01 version of VM * Update commit SHAs for 4 p4lang repos to latest as of 2021-Sep-07 * Update Ubuntu 20.04 README.md for how I created 2021-Sep-07 version of VM Co-authored-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
193 lines
6.4 KiB
Bash
Executable File
193 lines
6.4 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# Print commands and exit on errors
|
|
set -xe
|
|
|
|
# Sublime 3 install steps came from this page on 2020-May-11:
|
|
# https://www.sublimetext.com/docs/3/linux_repositories.html#apt
|
|
# The commands were modified only to remove 'sudo' from several
|
|
# commands. sudo is unnecessary here since this entire script is
|
|
# executed as the user root.
|
|
|
|
wget -qO - https://download.sublimetext.com/sublimehq-pub.gpg | apt-key add -
|
|
apt-get install apt-transport-https
|
|
echo "deb https://download.sublimetext.com/ apt/stable/" | tee /etc/apt/sources.list.d/sublime-text.list
|
|
# These commands are done later below
|
|
#apt-get update
|
|
#apt-get install sublime-text
|
|
|
|
# Atom install steps came from this page on 2020-May-11:
|
|
# https://flight-manual.atom.io/getting-started/sections/installing-atom/#platform-linux
|
|
|
|
wget -qO - https://packagecloud.io/AtomEditor/atom/gpgkey | apt-key add -
|
|
sh -c 'echo "deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main" > /etc/apt/sources.list.d/atom.list'
|
|
# These commands are done later below
|
|
#apt-get update
|
|
#apt-get install atom
|
|
|
|
apt-get update
|
|
|
|
KERNEL=$(uname -r)
|
|
DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" upgrade
|
|
apt-get install -y --no-install-recommends --fix-missing\
|
|
atom \
|
|
autoconf \
|
|
automake \
|
|
bison \
|
|
build-essential \
|
|
ca-certificates \
|
|
clang \
|
|
cmake \
|
|
cpp \
|
|
curl \
|
|
emacs \
|
|
flex \
|
|
g++ \
|
|
git \
|
|
iproute2 \
|
|
libboost-dev \
|
|
libboost-filesystem-dev \
|
|
libboost-graph-dev \
|
|
libboost-iostreams-dev \
|
|
libboost-program-options-dev \
|
|
libboost-system-dev \
|
|
libboost-test-dev \
|
|
libboost-thread-dev \
|
|
libelf-dev \
|
|
libevent-dev \
|
|
libffi-dev \
|
|
libfl-dev \
|
|
libgc-dev \
|
|
libgflags-dev \
|
|
libgmp-dev \
|
|
libjudy-dev \
|
|
libpcap-dev \
|
|
libpython3-dev \
|
|
libreadline-dev \
|
|
libssl-dev \
|
|
libtool \
|
|
libtool-bin \
|
|
linux-headers-$KERNEL\
|
|
llvm \
|
|
lubuntu-desktop \
|
|
make \
|
|
net-tools \
|
|
pkg-config \
|
|
python3 \
|
|
python3-dev \
|
|
python3-pip \
|
|
python3-setuptools \
|
|
sublime-text \
|
|
tcpdump \
|
|
unzip \
|
|
valgrind \
|
|
vim \
|
|
wget \
|
|
xcscope-el \
|
|
xterm
|
|
|
|
# TBD: Should these packages be installed via apt-get ? They are in
|
|
# my install-p4dev-v4.sh script, but they might not be needed, either.
|
|
|
|
# zlib1g-dev18
|
|
|
|
# On a freshly installed Ubuntu 20.04.1 or 18.04.5 system, desktop
|
|
# amd64 minimal installation, the Debian package python3-protobuf is
|
|
# installed. This is depended upon by another package called
|
|
# python3-macaroonbakery, which in turn is is depended upon by a
|
|
# package called gnome-online accounts. I suspect this might have
|
|
# something to do with Ubuntu's desire to make it easy to connect with
|
|
# on-line accounts like Google accounts.
|
|
|
|
# This python3-protobuf package enables one to have a session like
|
|
# this with no error, on a freshly installed system:
|
|
|
|
# $ python3
|
|
# >>> import google.protobuf
|
|
|
|
# However, something about this script doing its work causes a
|
|
# conflict between the Python3 protobuf module installed by this
|
|
# script, and the one installed by the package python3-protobuf, such
|
|
# that the import statement above gives an error. The package
|
|
# google.protobuf.internal is used by the p4lang/tutorials Python
|
|
# code, and the only way I know to make this work right now is to
|
|
# remove the Debian python3-protobuf package, and then install Python3
|
|
# protobuf support using pip3 as done below.
|
|
|
|
# Experiment starting from a freshly installed Ubuntu 20.04.1 Linux
|
|
# desktop amd64 system, minimal install:
|
|
# Initially, python3-protobuf package was installed.
|
|
# Doing python3 followed 'import' of any of these gave no error:
|
|
# + google
|
|
# + google.protobuf
|
|
# + google.protobuf.internal
|
|
# Then did 'sudo apt-get purge python3-protobuf'
|
|
# At that point, attempting to import any of the 3 modules above gave an error.
|
|
# Then did 'sudo apt-get install python3-pip'
|
|
# At that point, attempting to import any of the 3 modules above gave an error.
|
|
# Then did 'sudo pip3 install protobuf==3.6.1'
|
|
# At that point, attempting to import any of the 3 modules above gave NO error.
|
|
|
|
sudo apt-get purge -y python3-protobuf || echo "Failed to remove python3-protobuf, probably because there was no such package installed"
|
|
sudo pip3 install protobuf==3.6.1
|
|
|
|
# Starting in 2019-Nov, Python3 version of Scapy is needed for `cd
|
|
# p4c/build ; make check` to succeed.
|
|
sudo pip3 install scapy
|
|
# Earlier versions of this script installed the Ubuntu package
|
|
# python-ipaddr. However, that no longer exists in Ubuntu 20.04. PIP
|
|
# for Python3 can install the ipaddr module, which is good enough to
|
|
# enable two of p4c's many tests to pass, tests that failed if the
|
|
# ipaddr Python3 module is not installed, in my testing on
|
|
# 2020-Oct-17. From the Python stack trace that appears when running
|
|
# those failing tests, the code that requires this module is in
|
|
# behavioral-model's runtime_CLI.py source file, in a function named
|
|
# ipv6Addr_to_bytes.
|
|
sudo pip3 install ipaddr
|
|
|
|
# Things needed for PTF
|
|
sudo pip3 install pypcap
|
|
|
|
# Things needed for `cd tutorials/exercises/basic ; make run` to work:
|
|
sudo pip3 install psutil crcmod
|
|
|
|
useradd -m -d /home/p4 -s /bin/bash p4
|
|
echo "p4:p4" | chpasswd
|
|
echo "p4 ALL=(ALL) NOPASSWD:ALL" > /etc/sudoers.d/99_p4
|
|
chmod 440 /etc/sudoers.d/99_p4
|
|
usermod -aG vboxsf p4
|
|
|
|
cd /usr/share/lubuntu/wallpapers/
|
|
cp /home/vagrant/p4-logo.png .
|
|
rm lubuntu-default-wallpaper.png
|
|
ln -s p4-logo.png lubuntu-default-wallpaper.png
|
|
rm /home/vagrant/p4-logo.png
|
|
cd ~
|
|
|
|
# 2021-Mar-06 this command failed with an error that the file did not exist.
|
|
#sed -i s@#background=@background=/usr/share/lubuntu/wallpapers/1604-lubuntu-default-wallpaper.png@ /etc/lightdm/lightdm-gtk-greeter.conf
|
|
# The following command will hopefully cause the P4 logo to be normal
|
|
# size and centered on the initial desktop image, rather than scaled
|
|
# and stretched and cropped horribly.
|
|
#sed -i s@wallpaper_mode=crop@wallpaper_mode=center@ /etc/xdg/pcmanfm/lubuntu/desktop-items-0.conf
|
|
|
|
# If that does not have the desired effect, another possibility is
|
|
# executing that command to edit the same string in file
|
|
# /etc/xdg/pcmanfm/lubuntu/pcmanfm.conf
|
|
|
|
# TBD: Ubuntu 20.04 does not have the light-locker package, so it
|
|
# fails if you try to remove it. Probably enabling auto-login
|
|
# requires a different modification than is done below with the cat <<
|
|
# EOF command.
|
|
|
|
# Disable screensaver
|
|
#apt-get -y remove light-locker
|
|
|
|
# Automatically log into the P4 user
|
|
#cat << EOF | tee -a /etc/lightdm/lightdm.conf.d/10-lightdm.conf
|
|
#[SeatDefaults]
|
|
#autologin-user=p4
|
|
#autologin-user-timeout=0
|
|
#user-session=Lubuntu
|
|
#EOF
|