Separate distrinet from mininet

[atomassi]

The current structure of the project is not very clear as the code is fully merged with mininet.
In my opinion, it would be better to have a separate module that can be easily tested and installed on top of mininet.
A possible (abstract) structure for the distrinet core might be the following:

distrinet/
|-- distrinet/
|   |-- provisioning/
|   |    |--  aws/
|   |    |      |-- ...
|   |    |-- grid5k/
|   |    |      |-- ...
|   |    |-- commons/
|   |           |-- ...
|   |-- utils/
|   |    |-- ...
|   |-- ...
|-- setup.py
|-- requirements.txt
|-- tests
|-- ...

The main goals are:

• decouple distrinet from mininet, by building it as a module and not as just additional code
• make the code easier to be tested and maintained
• make the project easier to be extended by adding new modules (e.g., google, azure, etc) and define an API in forms of an abstract class to be followed and implemented by the provisioning methods

[dsaucez]

I will look at it.