search

10gen / mongo-orchestration

Apache License 2.0
7 stars 11 forks source link

Should be possible to configure which interfaces and protocols to bind #143

Closed acmorrow closed 9 years ago

acmorrow commented 9 years ago

Currently, there is no way to specify which interface to listen on, or whether to listen on IPv4, IPv6, both, etc.

This can make it difficult to communicate with mongo-orchestration on hosts offering multiple interfaces or multiple protocols, or both.

acmorrow commented 9 years ago

Similarly, if a request to create a mongod arrives via interface/proto X, then the mongod(s) that are started should also bind to that interface/proto, since otherwise if the request originated on a remote machine, the mongod procs that are started could not be reached.

This is necessary to support testing drivers on systems where mongod cannot run (e.g. ARM), so m-o must be run on a remote system.

llvtt commented 9 years ago

More work is still needed for making mongod/s bind to the same interface as MO.

TylerBrock commented 9 years ago

Right, that needs more work, but this is one step along the way. Thanks.

TylerBrock commented 9 years ago

Oh... actually the more I think about it, we may want to make those distinct: i.e. mongod binds to localhost but MO binds to 0.0.0.0.

llvtt commented 9 years ago

Since we created another issue for making mongo processes bind to a given interface (#149), I'll close this one, which only pertains to MO itself.