refactor deprecated API's to make cookbook chef v14 compatible #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixed typo in error messages, thanks mbj for the patch.
Fixed syntax error in libraries/mongodb.rb, thanks Reed Law for the patch.
…ng changed (fixes issue 5)
…a single directory with the name of the cookbook as root in the tarball
…umber in the resulting tarball.
…and added proper LSB header.
the --shardsvr and --configsvr option
… if no members are found. If chef-server is running the configuration print a warning and stop configuration.
…r for replicated shards this name will still be ignored,
and the name of the replicaset will be generated using 'rs_#{shard_name}'.
…ebinterface, per default it is turned off.
Fixed a link in Readme file.
This allows the user to override RPM install completely from their own recipe.
Add ability to reference a node.dns_alias property if available, instead of the fqdn. This allows definition of configservers using aliases, instead of the actual hostnames of the machines.
Since start_server() and restart_server() do not actually verify whether the port is open and receiving connections (even though mongo starts up, pre-alloc/other setup takes a few minutes), the replicaset recipe was failing to establish a connection with the db. The change to the initd file waits for the port to be open before proceeding, ensuring that the replicaset recipe will work. Fixes #17 (cherry picked from commit 3a91a28)
removes support for MongoDB 3.0 and earlier SCC config servers.
…han /data/application-data/mongodb/mongod.lock, as pidfile (see https://jira.mongodb.org/browse/SERVER-4523) - this gets the init script working on CentOS 7 within systemd sysv init compatibility mode
…mongo processes can live on the same machine correctly
…n to permit skipping the init.d script installation, in the case where a managed script is provided by the caller instead.
Make mongo gem version configurable
… processes, to essentially disable the stop script from doing a kill -9. We need this because stopping a mongo 4.4 process while the whole cluster isn't yet in 4.4 FCV compat mode takes more than 5 minutes, as it has to do a lengthy process to write its store back in a 4.2 backwards compatible mode. If the stop script kill -9's the process during this, then the db won't be able to be brought back up with 4.2 at all.
Up the waiting period on shutdown from 5 minutes to 3 hours for mongo…
…imeout increase service start timeout from 10m to 90m
…deprecated and no longer supported in chef v13 and later
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(see also https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00001QYStkYAH/view)