Roadmap to get this module in better shape

[h-haaks]

This module needs a few major changes to support later OS versions and mongodb versions.

This issue is created to see if we could gather around a set of smaller tasks to move the module in the right direction.

Feel free to add comments here, and I'll try to make an ordered list of tasks out of it.

Tasks

1. mongos: init.d scripts to systemd service unit
   mongob default versions:
   • redhat++ - bump repo version from 3.6 to 4.4
   • debian-10 - bump default version from 4.4.8 to 4.4.29
     Mongos as systemd service #698
2. default to using mongodb repo. Allow only 4.4+ repo versions
3. bump default repo version to 5.0
4. add rhel8 and debian11 support
5. remove debian10 support
6. cleanup?
7. release 5.0.0
8. support installing mongosh
9. add mongosh provider to custom types
10. use apt::keyring
11. add mongodb 6.0 and 7.0 support
12. add rhel9, debian12 and ubuntu22.04 support
13. release 5.x.0
14. remove mongodb 4.x support?

[h-haaks]

Task:
Switch to install from mongodb repos as default for all OS distros.

As of now I think only Ubuntu 20.04 have mongodb in their repos, and even Ubuntu 20.04 only have mongodb 3.8
Mongodb is removed in Ubuntu 22.04
Does anyone know SLES?

We have to decide what mongodb major version should be the new default.
Look like 5.x is the latest version supporting all platforms without mongosh.

DONE

[h-haaks]

Task:
Move repo install from globals to install.

I think of the globals class is more like params, and I don't like it to decalare any resources.

EDIT: decided to keep the globals class and remove all params classes

[h-haaks]

Task:
Add support for new OS releases

[h-haaks]

Task:
Add support for mongosh

See #677, but I think we should solve this by making side by side providers that use the new command.
By doing this we could keep the mongo provider default in the beginning and let users opt in to using the mongosh provider.

The old mongo command is removed in MongoDB 6.x

[h-haaks]

Task:
mongodb.conf to yaml

docs https://www.mongodb.com/docs/v4.4/reference/configuration-options/#file-format

EDIT: The existing config is actually yaml. It's just a bit strange looking with dot notation in keys.
May be we should take all config as an Hash and use toYAML() in the template?
That way the config class params don't limit what could be added to the file.

[h-haaks]

Task:
Switch to Apt::Keyring for apt sources

The use of Apt::Key is deprecated in the latest Debian and Ubuntu releases.

DONE

[h-haaks]

Task:
Use systemd service file for mongos on all OSes

https://github.com/voxpupuli/puppet-mongodb/blob/master/manifests/mongos/config.pp#L65

DONE

[stevenpost]

Suggested task:
Remove params class in favour of module data.

There is currently a mix of module data and the params class, the module should have either one, not both. This just does some cleanup, but keeps things backwards compatible. If you agree that this is a good idea, I get a PR ready.

@h-haaks I'm tasked with upgrading our existing MongoDB setup to version 6.x, it is currently using version 4.4. So I'm currently invested to get this module into shape and get in proper support for 6.x.

DONE

[h-haaks]

@stevenpost I'm kind of in the same spot.

I was thinking about creating a mongodb ( init.pp ) class and move away from globals.
I also think the Vox Pupuli practice is to only use hirera data for params that vary based on OS etc.

If you like to help feel free to have a look at it.
I'm currently working on bumping minor repo version to 4.4 and fixing outdated configs ...

[stevenpost]

Do you want to keep the module backwards compatible between 4.x and 5.x? I guess not, since it's a major release.

How far back do we need to support old versions of MongoDB?

[witjoh]

Do you want to keep the module backwards compatible between 4.x and 5.x? I guess not, since it's a major release.

How far back do we need to support old versions of MongoDB?

See also #695

As from version 6.0, mongo cli is removed and replaced by mongosh. Mongosh does work with version 4.4.
I haven't encountered any breakage working on this module to try to add support for 5.x and 6.x. But I can't guarantee it.

Moving to mongosh only will be the first big step to get the newer versions working with this module.

Other changes like support for newer OS versions, move away from params.pp will probably not impact mongodb version compatibility ?

Also, mongodb 4.4 reached end of life 2 weeks ago (https://www.mongodb.com/legal/support-policy/lifecycles)

And one can always put in the docs, to use this module current version (v4.2.0) for mongo prior to 5.x.

[stevenpost]

Considering 4.4 has reached EOL, I would drop support for it, and only support 5.0 and up.

[h-haaks]

Oh right.
My thought was to drop really old versions at first in a release with updated module dependencies and updated OS support.
We could drop 4.4 in the first release I just wanted not to force product upgrade in the first module release in a long time.