Implement auth on mongodb

[Luke Hinds]

Mongodb currently runs with noauth on the undercloud / controller roles.

The current arch is not exposing a security risk as on the undercloud the bind_ip is 127.0.0.1 (for zaqar DB) and on the controller listening is restricted to the internal API network "InternalApiNetCidr" (for ceilometers DB).

It is still however a prudent effort to further 'shore up' extras layers of defence by implementing auth.

[Ben Nemec (bnemec)]

Given that this is a security layering bug (so not an immediate vulnerability) and adding auth to a service which previously didn't have it is likely to be a somewhat invasive change, I'm going to move it out to Queens. I'd prefer to do something like this early in the cycle so we have time to tease out issues, especially with composable services that may not be well-tested in ci.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE