* p4runtime_lib/helper: use more appropriate variable names
Suggested-by: Antonin Bas <abas@vmware.com>
Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
* utils: show error message when priority is missing
A 'priority' field is required to order entries when the
table's match key includes an optional, ternary or range match.
Suggested-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
* 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>
* 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
P4Runtime uses a "complex" error message format to report errors for
batched Write & Read RPC requests. Some effort is required to parse the
error messages appropriately in order to print some useful debugging
information.
Running the exercises can race:
$ make run
mkdir -p build pcaps logs
p4c-bm2-ss --p4v 16 --p4runtime-file build/basic.p4info --p4runtime-format text -o build/basic.json basic.p4
sudo python ../../utils/run_exercise.py -t topology.json -b simple_switch_grpc
Reading topology file.
Building mininet topology.
Switch port mapping:
s1: 1:h1 2:s2 3:s3
s2: 1:h2 2:s1 3:s3
s3: 1:h3 2:s1 3:s2
Configuring switch s3 using P4Runtime with file s3-runtime.json
- Using P4Info file build/basic.p4info...
- Connecting to P4Runtime server on 127.0.0.1:50053 (bmv2)...
- Setting pipeline config (build/basic.json)...
Traceback (most recent call last):
File "../../utils/run_exercise.py", line 408, in <module>
exercise.run_exercise()
File "../../utils/run_exercise.py", line 207, in run_exercise
self.program_switches()
File "../../utils/run_exercise.py", line 312, in program_switches
self.program_switch_p4runtime(sw_name, sw_dict)
File "../../utils/run_exercise.py", line 284, in program_switch_p4runtime
proto_dump_fpath=outfile)
File "/home/p4/tutorials/utils/p4runtime_lib/simple_controller.py", line 120, in program_switch
bmv2_json_file_path=bmv2_json_fpath)
File "/home/p4/tutorials/utils/p4runtime_lib/switch.py", line 85, in SetForwardingPipelineConfig
self.client_stub.SetForwardingPipelineConfig(request)
File "/usr/local/lib/python2.7/dist-packages/grpc/_interceptor.py", line 141, in __call__
return call_future.result()
File "/usr/local/lib/python2.7/dist-packages/grpc/_channel.py", line 272, in result
raise self
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.PERMISSION_DENIED, Not master)>
../../utils/Makefile:27: recipe for target 'run' failed
make: *** [run] Error 1
Fix that by waiting for one response after sending MasterArbitrationUpdate.
Signed-off-by: Alex Badea <alex.badea@keysight.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)
