Itests archetype.
Merge branch 'develop' of https://github.com/dana-i2cat/opennaas into feature/itests-archetype
SampleResource unitary and integration tests.
Merge pull request #735 from adrian-rosello/feature/itests-archetype

Feature/itests archetype
Merge pull request #736 from adrian-rosello/feature/sample-resource-itest

SampleResource unitary and integration tests.
Merge pull request #739 from isartcanyameres/feature/allocate-most-specific-flow

NCLController accepts SDNNetworkFlow as parameter in allocateFlow().
Typo error in blueprint for RequestToFlowLogic class. Renamed to RequestToFlowsLogic according to the interface name it implements.
Merge pull request #740 from adrian-rosello/fix/ncl-typo-error

Change RequestToFlowLogic class name to RequestToFlowsLogic
Bug in class definition.
Merge pull request #741 from adrian-rosello/fix/ncl-typo-error

Bug in class definition.
NCL respects the IPs provided in createRequest call.
Merge pull request #742 from adrian-rosello/features/flow-with-ip

NCL respects the IPs provided in createRequest call.
Set ToS correct value.
Merge pull request #743 from adrian-rosello/features/flow-with-tos

Set ToS correct value.
Renaming of Flow -> Circuit and test fixed.
Save allocated sdnflows per circuit.
Merge pull request #744 from adrian-rosello/feature/multiple-flow-per-flowreq

Renaming of Flow to Circuit
Logic and test to create most specific flow given a FlowRequest.

Only ethernetType value has been added to the match, the rest was already behaving as expected.

Related to task:
http://jira.i2cat.net:8080/browse/OPENNAAS-1183
Fix error in tests regarding ToS value.

ToS value in FlowRequest is the decimal representation of the whole ToS byte.
Due to 7th and 8th bits being reserved, ToS value SHOULD be multiple of 4.

However, ToS value in FloodlightOFMatch is the decimal representation of only
the 6 non-reserved bits of the ToS byte.

Tests where using 1 as FlowRequest ToS value, which does not correspond to a valid one.
Additionally, tests were assuming tos values in FlowRequest and in generated FloodlightOFMatch shoud be equals, which is not the case.

More information regarding the confusion can be found here:
http://www.tucny.com/Home/dscp-tos

This patch documents methods regarding ToS in FlowRequest to clarify its meaning and expected values,
and updates test to behave as desired.