Forecast component:

- Fixed Dockerfile dependencies
- Updated TODO.txt file

src/forecaster/Dockerfile

@@ -63,6 +63,7 @@ RUN python3 -m pip install -r requirements.txt
 # Add component files into working directory
 WORKDIR /var/teraflow
 COPY src/context/. context/
+COPY src/device/. device/
 COPY src/forecaster/. forecaster/
 COPY src/monitoring/. monitoring/
 

src/forecaster/service/TODO.txt

 
-Use a smaller network:
-INFO     forecaster.tests.Tools:Tools.py:75 Discovering Devices and Links...
-INFO     forecaster.tests.Tools:Tools.py:104   Found 22 devices and 462 links...
-
-In topology forecaster, the data file should contain more than 1 row per link, otherwise, it crashes with no enough samples.
-
-- implement integration with pathcomputation
-
-
-test case:
-- instantiate Context and Monitoring
-- populate topology
-- populate monitoring timeseries with link utilizations
-- run test for link
-- run test for topology
-
-
 ## PathComp Impact
 After retrieving the topology, if the service has a duration constraint configured, the PathComp component should interrogate the Forecaster and request a topology forecast according to the requested duration of the service. The computed link capacity forecast should be used as link capacity in path computations.