Release 2.3.1

Changes to the DMK in 2.3.1

Changes made to DMK 2.3.1

Here are the main changes introduced by DMK 2.3.1:

• set_local_dmk_config.py script was added to quickly change local DMK configuration (which overrides the global configuration file). To use it, simply run set_local_dmk_config.py SECTION VAR_NAME NEW_VALUE, for instance set_local_dmk_config.py mdb01 MONGO_DATA "/u02/mongo/data". See Environment variables for more details.

• DMK is more versatile, with more options to customize paths for main variables (DMK_HOME, MONGO_BASE, etc.)

• Some bug corrections, code cleaning and internal testing enhancements.

If you are updating from a version of DMK older than 2.3.0, read the following section, which still applies to DMK 2.3.1.

Changes made to DMK 2.3.0

Replacement of Perl scripts with Python

All Perl scripts of DMK have been replaced by Python scripts. Most features work exactly in the same way as before.

DMK configuration file

Before release 2.3.0, only one configuration file existed in $DMK_HOME/etc. There is now a second configuration file in ~/.DMK/dmk.conf.local, which will overwrite default configuration options. See Using DMK for more information.

New scripts

Most scripts functionalities were kept in release 2.3.0, but some were renamed to add clarity:

• dmk_db_ctl.sh is now dmk_db_ctl.py. Its usage is detailed in Starting & Stopping MongoDB instances.

• dmk_dbcreate.sh is now dmk_dbcreate.py. Its usage is detailed in Creating a MongoDB instance.

• dmk_dbbackup.sh is now dbk_dbbackup.py. Its usage is detailed in Backing up databases.

• dmk_run.sh is now dmk_status.py.

New default directories

Before release 2.3.0, the default behavior was to place every MongoDB files in either in /u01 or /u02. Important structural changes were made, to meet MongoDB best practices:

• Data files now default to MONGO_DATA_ROOT=/u02/mongodb/data/<instance_name>

• Journals now default to MONGO_JOURNAL_ROOT=/u03/mongodb/journal/<instance_name>

• Logs now default to MONGO_LOG_ROOT=/u04/mongodb/data/<instance_name>

You should overwrite the default variables in your dmk.conf.local configuration file when updating DMK.

New aliases and environment variables

Some aliases were changed in this release, others were added. See Environment Variables and Aliases for more information.

• mgstart, mgstop, mgrestart are new aliases to manage a MongoDB instance.

• vic now opens the MongoDB instance configuration file.

• vilst now opens the $DMK_HOME/etc/mongodb.lst file.

• sta, lsta, tsta, rsta are new aliases for instance status display.

• vil, cdl, tal are new aliases to view, access and tail log files of MongoDB instances.

• dmkc opens DMK default configuration file.

• dmkl opens DMK local configuration file, which overrides the default configuration file

Other changes

• Backups are no longer compressed by default. To enable gzip compression, use the -o="--gzip" option with the dmk_dbbackup.py script. You can also use the --archive option to write the backup to a single archive file.

• Binaries directory: By default, DMK will create instances in folders with full version names (8.0.16, for instance) instead of the old reduced format (8.0, for instance). This will ease out of place patching and adds clarity to the environment.

• The credential file must now be named cred.yaml (instead of cred.yml) and follow this format:

dmk_user: "#VALUE"
dmk_pwd: "#VALUE"