use dp_desc for module name in logging

[billsnow]

Status: Open Project: Flowvisor Component/s: Core Affects Version/s: 0.7.2 Fix Version/s: Next

Type: Improvement Priority: Minor Reporter: Nick Bastin Assignee: Rob Sherwood Resolution: Unresolved Votes: 0 Labels: None Remaining Estimate: Not Specified Time Spent: Not Specified Original Estimate: Not Specified

Description
currently logging uses dpid, which is not terribly human readable. What would be idea would be to get the stats_desc message and use the dp_desc for logging, i.e., Oct 5 16:28:31 flowvisor flowvisor: DEBUG-slicer_production_dpid:40026f11c2900: send to controller: ofmsg:v=1;t=FEATURES_REPLY;l=320;x=0;ports=6 becomes Oct 5 16:28:31 flowvisor flowvisor: DEBUG-slicer_production_switch5.stanford.edu: send to controller: ofmsg:v=1;t=FEATURES_REPLY;l=320;x=0;ports=6

Comments
Comment by Rob Sherwood [ 04/Jul/11 ] note that this would involve a bit of non-obvious work in that the file regress/fvregress.py that forms the main part of the regression harness makes assumptions about what FV sends during it's initial handshake. Not horrible to update, but this was my python code before I started really working in python

Original issue: https://openflow.stanford.edu/bugs/browse/FLOWVISOR-7