Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about listeners/setup (espeicially in Docker) #10

Closed
JohnOmernik opened this issue May 24, 2017 · 3 comments
Closed

Question about listeners/setup (espeicially in Docker) #10

JohnOmernik opened this issue May 24, 2017 · 3 comments

Comments

@JohnOmernik
Copy link

I am looking to run this in Apache Mesos (great setup by the way) based on the architecture page, it looks like I can run multiple instances of this to sync up together for HA etc, however, because they use multicast, I'd have to run my docker daemons in host mode for that to work? (Please correct me if I am wrong).

Thanks!

@mehrdadrad
Copy link
Collaborator

@JohnOmernik I haven't tried it with Apache Mesos.

@JohnOmernik
Copy link
Author

So it's not really related to Mesos (the question). I am more asking about running with multiple instances of vflow working together. I.e. if they are tied together using multicast as the approach... that won't be possible if you are running vflow in docker and using bridge mode. Correct? This requires us to run the docker containers in host mode so the daemon can actually listen on a host multicast address... not a bridged one... is this correct?

If this is the case, could we consider providing a list of "other" vflow node IP/Ports to have nodes try to register with rather than using Multicast?

Thanks

@mehrdadrad
Copy link
Collaborator

I think bridge mode should work. it doesn't have any config in regard to multicast nodes but that's nice to add this feature. in case the multicast doesn't work you just lose data once you start the vFlow for first time (short time based on the device template interval configuration) and once a template added in device(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants