Mongo 3.4 and (partial) Xenial support #32
+17
−23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request would:
signing_key
ansible_distribution_release
in APT sources, or fallback to the previously hard-coded valuesMongoDB Xenial repositories now provide the needed systemd unit at least for 3.2 and 3.4 so there's no need to build one manually.
The
service
in Ansible system module seems to enable the systemd service and start it properly when run on real server, but when running Ubuntu 16.04 in Docker the setup fails withno service or tool found for: mongod
which is probably because Ansible showsupstart
inansible_service_mgr
when run on image built from Ubuntu official 16.04 base image.I did deploy a working MongoDB 3.4 on Xenial with the currently release version with this in my
group_vars
:which is what this pull request should produce.
mongodb_transparent_hugepage_disable
does not work with this pull request on systemd because it creates an upstart file and I didn't do anything to it. And as mentioned there's a Docker problem, hopefully you have better insight in it than I do.