Evaluate Traefik (NginX Replacement) about mainflux HOT 10 CLOSED

@nmarcetic any thoughts?

from mainflux.

@darkodraskovic Idea is awesome and its made with go ;) Its still young project and I am really skeptic.
Nginx is really big name and I am happy with it.
We should definitely stay tuned and follow the project, maybe even try to make a POC later and compare results, do benchmark. I really like dynamic idea :)

from mainflux.

@nmarcetic I think general flow should be TDD oriented:

• Write tests
• Implement (PoC in this case)
• If it pass you are OK

I.e. if Traefik passes our tests (and requirements) we're good to go, no matter the project maturity.

I am not against NginX, but from what I have been reading for MQTT people usually falled back to Haproxy (because DNS/IP load-balancing and some other stuff).

Since we are Go and Docker oriented we must take some risks and best bets on modern technology ;).

BTW: this Cisco project: http://mantl.io/ is using Traefik. This is enough for me to believe it is production-ready.

Looking at the same project here: https://github.com/CiscoCloud/mantl#core-components, it is pretty close to the DevOps stack we had in mind (maybe overkill, but not so far away).

from mainflux.

@mijicd @nmarcetic I think before proceeding with mainflux-devops we should seriously evaluate Cisco Mantl: http://mantl.io/

It uses bunch of technologies we wanted to use anyway - Traefik, Kubernetes, Vault and Ansible.

It also adds UI to handle the deployments.

@mijicd I can see here: http://mantl.io/technologies that it has a support from Elastic Search also, as an add-on.

from mainflux.

@mijicd if you are OK with Mantl, ad us a few comments - what are your findings so far? What about Traefik? What about Elastic Search add-on (and adding add-ons in general with Mantl)?

from mainflux.

Some facts:

• Mantl is consisted of top notch tools, with each of them exposing a simple yet powerful management UI.
• ELK stack is one of the available add-ons, as you said. I'm still investigating the way they're intended to be used. We should not have any problems with it, since we have a safe fallback in deploying each piece of ELK as a separate container in case that anything goes wrong with add-on setup.
• Traefik is already a part of Mantl, so it is pretty clear that by choosing Mantl we're going to choose Traefik as well. It is performant, quite simple to configure, and it is written in golang :)

from mainflux.

Cool. We have enough data to ACK Mantl and Traefil. I will close the issue.

from mainflux.

Hi,

I have an existing traefik ingress controller servicing other parts of the cluster. Would it be especially difficult to point it at mainflux?

Can it replace nginx? Or should I point it to the mainflux nginx? I am unsure if you use nginx in any ways which is special enough to make removing or replacing it difficult.

Thanks

from mainflux.

It should be relatively easy to replace NginX Ingress - Traefik should be capable to replace it.

Please try it and let us know about the progress.

from mainflux.

Thanks. I have 4 hours experience with mainflux on kubernetes, and less than a day with Traefik on kubernetes. Working on migrating (many) docker/compose deployments to k8s.

I probably need more than "it should be relatively easy", but so far nginx and traefik are co-existing, and I seem to be able to have traefik handle the ssl certs, and forward connections to nginx for mainflux... (at least for the GUI).

However I'm sure there will be plenty of breakage...

• first victim was MQTT.
• next will likely by CoAP..

from mainflux.