-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MongoDB Rework #43
MongoDB Rework #43
Conversation
@kotfic PTAL. I don't have access to any resources that I can test this on. Could I send you some playbooks to try on AWS? Hopefully, this shouldn't require much more work to handle the simple case of just installing a stand alone MongoDB. |
@opadron do you have a motivating use-case for the sharding and replication set work? I can deploy to some virtual machines locally to test these out, but they are features of mongo that I am not particularly familiar with, I'll need a pretty straightforward use-case and test playbook. |
For now, I think the current example playbook should be enough to reproduce a standalone install of mongo (with a newer version than what's in ubuntu's repos). - hosts: mongodb
roles:
- role: mongodb
state: started |
f1481d6
to
8e021d4
Compare
8e021d4
to
c1ded81
Compare
…andalone shards using the wrong port
@Kitware/gobig Ready for review. |
@opadron looks like there are some string mangling issues (there is a \n in the download url)?
|
Fixed. Apparently, when you use syntax like the one below for a string block: my_string: >
long string that I didn't expect to have a newline at the end you get a newline tacked onto the end. Someday, I will understand YAML's syntax. I can dream. |
ansible script is now completing but mongod is throwing an error. From
|
@kotfic PTAL |
@opadron LGTM! |
More and more, I'm finding that simple updates to GoBig seldom turn out so simple. This PR, originally meant as just a fix to #42, is a testament to this observation.
Once I switched the mongodb roles to being proper roles (as opposed to dumb wrappers around apt), I knew I needed to add configuration options to meet the inevitably varied needs of those who might want to use them. The more I dug into the docs, though, the more apparent the need to cover use cases requiring replica sets and sharding became.
This code is indeed a WIP, but it should help others to see what I'm going for.