make sure the job accounting info is not updated if the job is not in executing state
skip bandwidth calculatation if previous and current timestamp diff is too small, just use the previous bandwidth usage
update time interval threshold and add additional check condition
fix divide by 0 bug
remove the additional check because it can result in inaccurate bandwidth usage data sometimes
initial implementation of adding openvswitch support to lark code
add ovs_set_bridge_fd function
when deal with ovs bridge, we just disable stp and does not check port state
added ovs_delete_interface_from_bridge; made some tweaks in executed ovs related commands to make them work when the bridge or port is already existed
add ovs QoS rate limitng & minor fixes
also delete the external_device interface from bridge (if exists) before adding it to bridge to make sure the interface is always newly connected
update bandwidth management to use openvswitch egress QoS
added LarkBandwidthManagment directory which has README, example of local config and exmaple program for determining bandwidth included.
Merge pull request #9 from zhangzhehust/network_namespaces

Working openvswitch support and lark bandwidth management