Dockerize the REST API

[fasten-project]

Dockerize the REST API

[proksch]

Make it as simple as possible. I would not tie it to the FASTEN Server, as it is not a plugin.

[gousiosg]

The idea was that if we use it as part of the server, we would be able to reuse the same build, deployment and K8S pipeline. When I wrote that comment, you had to run the Rest API in a screen session, with no supervision etc. If this is the fastest way to do that, so be it for the moment. Eventually, we need to deploy it within K8S.

[gousiosg]

Why not reuse the existing infrastructure and link with our plug-in runner component?

[marcomicera]

Why not reuse the existing infrastructure and link with our plug-in runner component?

@proksch mentioned in an email that there will be a k8s deployment in the future, and @wzorgdrager would assist me with that.

[gousiosg]

This answer is orthogonal to my question. Yes @wzorgdrager will help with the deployment files, but we should use the existing docker building infrastructure to deploy

[marcomicera]

but we should use the existing docker building infrastructure to deploy

I was simply not aware of that

Why not reuse the existing infrastructure and link with our plug-in runner component?

because Docker hasn't been mentioned here.

@gousiosg could you please tell me where can I find this infrastructure and what it is about?

[MihhailSokolov]

@marcomicera @gousiosg is there any progress on this one?

[MihhailSokolov]

@gousiosg by reusing existing Docker deployment you mean making it a plugin and deploying it with the FASTEN server the same way we deploy other plugins?
If yes, I actually think it is not quite necessary. REST API does not need to consume from Kafka (or any other place), so it doesn't really need the FASTEN server. So I think it is easier to deploy it separately. What do you think?

[marcomicera]

@marcomicera @gousiosg is there any progress on this one?

No, I didn't work on this.