search

openbudgets / DAM

OBEU Data Analysis and Mining repository
3 stars 1 forks source link

DAM workflow #16

Open skarampatakis opened 7 years ago

skarampatakis commented 7 years ago

I thought that the workflow was that Indigo would communicate with DAM to set analytics tasks and get the results. No connection with the actual servers.

But it seems that this is not the case as Indigo asks directly the specific endpoint. That means that each analytics processing server should be accessible publicly?

I don't know if this is safe enough. It would be much more secure if only DAM would communicate with the processing servers. Also I believe we could then avoid the timeout errors.

HimmelStein commented 7 years ago

Indigo should only communicate with DAM, and DAM will schedule data-mining tasks at particular server.

larjohn commented 7 years ago

@skarampatakis this was the plan, but there are still some difficulties (there are issues here and in the integration repo) that forced a temporary revert to the old method of interaction, so that we can be represented in re:publica.

skarampatakis commented 7 years ago

Now that re:publica has passed I think we should try to work on this as I have some concerns over exposure of at least opencpu container on public.