They refer to bash script names that do not exist in the
vm-ubuntu-20.04 directory, and it is not straightforward and quick to
update those instructions to use scripts in the vm-ubuntu-20.04
directory without making a fair number of changes, and probably
several hours of testing those changes, that I am not prepared to make
any time soon.
The instructions _might_ be correct for the vm directory when starting
with an Ubuntu 16.04 Linux system, but that version of Ubuntu is no
longer supported, and I do not think we should be recommending its
use.
* Updated the utils/run_exercise.py to allow exercises to customize
host configuration from the topology.json file.
Now hosts and `ping` each other in the basic exercise. Other Linux
utilities should work as well (e.g. iperf).
```
mininet> h1 ping h2
PING 10.0.2.2 (10.0.2.2) 56(84) bytes of data.
64 bytes from 10.0.2.2: icmp_seq=1 ttl=62 time=3.11 ms
64 bytes from 10.0.2.2: icmp_seq=2 ttl=62 time=2.34 ms
64 bytes from 10.0.2.2: icmp_seq=3 ttl=62 time=2.15 ms
^C
--- 10.0.2.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 2.153/2.540/3.118/0.416 ms
mininet> pingall
*** Ping: testing ping reachability
h1 -> h2 h3
h2 -> h1 h3
h3 -> h1 h2
*** Results: 0% dropped (6/6 received)
```
Only updated basic exercise, still need to update other exercises.
Also, updated the root-bootstrap.sh because I was running into issues
with latest version of vagrant.
* Accidentially added the solution to the basic exercise in the previous
commit. Undoing that here ...
* Updated the topology.json file and table entries for the basic_tunnel
exercise.
* Updated P4Runtime exercise with new topology and table entries.
* Fixed MAC addresses in P4Runtime exercise. It is working now.
* Fixed MAC addresses in P4Runtime exercise starter code
* Updated ECN exercise to use new topology.json file. Updated the
table entries / MAC addresses as well.
* Updated the topology.json file and table entries for the MRI exercise.
* Updated source_routing exercise with new topology file and verified
correct functionality.
* Updated load_balance exercise with new topology.
* Moved basic exercise triangle topology into a separate folder
* Added new topology for the basic exercise: a single pod of a fat-tree.
* Updated Makefiles and run_exercise.py to allow exercises to configure
each switch with a different P4 program. This is mainly for the
firewall exercise.
* Updated Makefiles of project to work with new utils/Makefile
* Updated load_balance and p4runtime exercise Makefiles
* Initial commit of the firewall exercise, which is a simple stateful
firewall that uses a bloom filter. Need to update README files
* Initial commit of the path_monitor exercise. It is working but still
need to update the README and figure out what we want the tutorial
attendees to implement.
* Updated README file in firewall exercise. Also removed the bits
from the starter code that we want the tutorial attendees to
implement
* Renamed path_monitor exercise to link_monitor
* Updated the README in the link_monitor exercise and removed the
bits from the starter code that we want the tutorial attendees
to implement.
* Updated README for the firewall exercise
* Adding pod-topo.png image to basic exercise
* Added firewall-topo.png image to firewall exercise
* Added link-monitor-topo.png to link_monitor exercise
* Updated README files to point to topology images
* Updated top-level README to point to new exercises.
* Fixed link for VM dependencies script in README
* Updated bmv2/pi/p4c commits
* Updated README files for exercises to fix some typos and added
a note about the V1Model architecture.
* Added a note about food for thought in the link_monitor README
* Updated the firewall.p4 program to use two register arrays rather
than a single one. This is to make the design more portable to
high line rate devices which can only support a single access
to each register array.
* Minor fix to firewall exercise to get rid of compiler warning.
* Updated comment in firewall exercise.
* Minor (typo) fixes in the firewall ReadMe
* More info in firewall exercise ReadMe step 2
* Updated firewall.p4 to reuse direction variable
* More testing steps, small fixes in firewall exercise Readme
* Added food for thought to firewall Readme
* Cosmetic fixes to firewall ReadMe
* Made a few updates to the basic exercise README and added more
details to the link_monitor exercise README.
Also added a command to install grip when provisioning the VM.
This could be useful for rendering the markdown README files offline.
* Updated top level README so it can be merged into the master branch.
* Moved cmd to install grip from root-bootstrap to user-bootstrap
* Adapt script to any machine
Adapt script to any machine, independent of the user. We support for installations in VM Ubuntu
* Clear user-bootstrap.sh
* Update user-bootstrap.sh
* Adapt installation script to any machine
* Update user-bootstrap to use latest version (#251)
* p4c tests are failing in latest version. So, let's skip it during vagrant provisioning
* Update tutorial to use latest version of P4 tools
Modify switch.py to handle setting default_action
Use --p4runtime-files instead of deprecated --p4runtime-file and
--p4runtime-format flags
Provide standard_metadata for mark_to_drop
* Fix path for ECN exercise
Add some hints to common issues users may run into
when following the README to run the tutorials.
Signed-off-by: Niranjhana Narayanan <niranjhana@outlook.com>
* Repository reorganization for 2018 Spring P4 Developer Day.
* Port tutorial exercises to P4Runtime with static controller (#156)
* Switch VM to a minimal Ubuntu 16.04 desktop image
* Add commands to install Protobuf Python bindings to user_bootstrap.sh
* Implement P4Runtime static controller for use in exercises
From the exercise perspective, the main difference is that control plane
rules are now specified using JSON files instead of CLI commands. Such
JSON files define rules that use the same name for tables, keys, etc. as
in the P4Info file.
All P4Runtime requests generated as part of the make run process are
logged in the exercise's “logs” directory, making it easier for students
to see the actual P4Runtime messages sent to the switch.
Only the "basic" exercise has been ported to use P4Runtime.
The "p4runtime" exercise has been updated to work with P4Runtime
protocol changes.
Known issues:
- make run hangs in case of errors when running the P4Runtime controller
(probably due to gRPC stream channel threads not terminated properly)
- missing support for inserting table entries with default action
(can specify in P4 program as a workaround)
* Force install protobuf python module
* Fixing Ctrl-C hang by shutdown switches
* Moving gRPC error print to function for readability
Unforuntately, if this gets moved out of the file, the process hangs.
We'll need to figure out how why later.
* Renaming ShutdownAllSwitches -> ShutdownAllSwitchConnections
* Reverting counter index change
* Porting the ECN exercise to use P4 Runtime Static Controller
* updating the README in the ecn exercise to reflect the change in rule files
* Allow set table default action in P4Runtime static controller
* Fixed undefined match string when printing P4Runtime table entry
* Updated basic_tunnel exercise to use P4Runtime controller.
* Changed default action in the basic exercise's ipv4_lpm table to drop
* Porting the MRI exercise to use P4runtime with static controller
* Updating readme to reflect the change of controller for mri
* Update calc exercise for P4Runtime static controller
* Port source_routing to P4 Runtime static controller (#157)
* Port Load Balance to P4 Runtime Static Controller (#158)
