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)
