mongodb listens only on IPv4, with no way to bind to IPv6

[Dan Sneddon]

In the puppetlabs_mongodb module, we do not set net.ipv6 to any value, resulting in IPv6 being disabled entirely in mongo. I am adding IPv6 native support to TripleO deployments (and hence RDO), but this value needs to be set in order to use IPv6.

If it is not desired to have IPv6 enabled in all cases, we can make this a value that may be set with Heat parameters. Heat can pass True in the case where IPv6 is desired and False in the default case, but the Puppet module will have to be modified to accept a boolean value for this configuration parameter.

From the MongoDB docs [1]:

 net.ipv6

    Type: boolean

    Default: False

Enable or disable IPv6 support and allows the mongos or mongod to connect to the MongoDB instance using an IPv6 network. All MongoDB programs and processes disable IPv6 support by default.

[1] - https://docs.mongodb.org/manual/reference/configuration-options/

[Emilien Macchi (emilienm)]

The bug is not in puppet-ceilometer but in puppetlabs-mongo iiuc.
The repo is located here: https://github.com/puppetlabs/puppetlabs-mongodb
They have their own bug tracker (Jira). Feel free to submit the bug there.

Thanks

[Emilien Macchi (emilienm)]

The link to report a bug in puppetlabs-mongodb is:
https://tickets.puppetlabs.com/browse/MODULES/component/11459/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel

Otherwise you can send a pull-request directly on github.