mongodb-automation

mongodb-automation is a docker image that allows you to deploy MongoDB instances using MMS Automation service. The image provides a pre-installed and configured MMS Automation agent.

See image in Docker Hub.

Examples

Running a single container

Launch a single mongodb-automation container where we are going to deploy one or more mongod instances:

docker run -d \
    -p 27017:27017 \
    mcascallares/mongodb-automation:latest \
    --mmsBaseUrl=https://mms.mongodb.com \
    --mmsGroupId=<your_mms_group_id> \
    --mmsApiKey=<your_mms_api_key>

From the MMS interface configure MongoDB to deploy with the desired options.

Running a 3-nodes replica set across multiple containers

To run across multiple containers you need some discovery mechanism to provide connectivity among docker containers. A common approach is to use logical names and DNS.

In this example I will use Skydock to provide DNS resolution. The DNS server will be listening on 172.17.42.1:53.

# running a DNS container with Skydns
docker run -d \
    -p 172.17.42.1:53:53/udp \
    --name skydns crosbymichael/skydns \
    -nameserver 8.8.8.8:53 \
    -domain docker


# running Skydock container to hook docker events with DNS updates
docker run -d \
    -v /var/run/docker.sock:/docker.sock \
    --name skydock crosbymichael/skydock \
    -ttl 30 \
    -environment dev \
    -s /docker.sock \
    -domain docker \
    -name skydns


# running 3 mongod processes in 3 different containers, one agent per container.
docker run -d \
    --name mongod1 \
    -h mongod1.mongodb-automation.dev.docker \
    --dns 172.17.42.1 \
    -p 27017:27000 \
    mcascallares/mongodb-automation:latest \
    --mmsBaseUrl=https://mms.mongodb.com \
    --mmsGroupId=<your_mms_group_id> \
    --mmsApiKey=<your_mms_api_key>


docker run -d \
    --name mongod2 \
    -h mongod2.mongodb-automation.dev.docker \
    --dns 172.17.42.1 \
    -p 27018:27000 \
    mcascallares/mongodb-automation:latest \
    --mmsBaseUrl=https://mms.mongodb.com \
    --mmsGroupId=<your_group_id> \
    --mmsApiKey=<your_mms_api_key>


docker run -d \
    --name mongod3 \
    -h mongod3.mongodb-automation.dev.docker \
    --dns 172.17.42.1 \
    -p 27019:27000 \
    mcascallares/mongodb-automation:latest \
    --mmsBaseUrl=https://mms.mongodb.com \
    --mmsGroupId=<your_group_id> \
    --mmsApiKey=<your_mms_api_key>

Using fig

We can deploy the same idea described in the point below but using a single entry point with fig:

skydns:
    image: crosbymichael/skydns
    command: -nameserver 8.8.8.8:53 -domain docker
    ports:
        - 172.17.42.1:53:53/udp
    dns: 172.17.42.1

skydock:
    image: crosbymichael/skydock
    command: -ttl 30 -environment dev -s /docker.sock -domain docker -name skydns
    volumes:
        - /var/run/docker.sock:/docker.sock

mongod1:
    image: mcascallares/mongodb-automation:latest
    command: >
        --mmsBaseUrl=https://mms.mongodb.com
        --mmsGroupId=<your_mms_group_id>
        --mmsApiKey=<your_mms_api_key>
    hostname: mongod1.mongodb-automation.dev.docker
    ports:
        - 27017:2700
    dns: 172.17.42.1

mongod2:
    image: mcascallares/mongodb-automation:latest
    command: >
        --mmsBaseUrl=https://mms.mongodb.com
        --mmsGroupId=<your_mms_group_id>
        --mmsApiKey=<your_mms_api_key>
    hostname: mongod2.mongodb-automation.dev.docker
    ports:
        - 27018:2700
    dns: 172.17.42.1

mongod3:
    image: mcascallares/mongodb-automation:latest
    command: >
        --mmsBaseUrl=https://mms.mongodb.com
        --mmsGroupId=<your_mms_group_id>
        --mmsApiKey=<your_mms_api_key>
    hostname: mongod3.mongodb-automation.dev.docker
    ports:
        - 27019:2700
    dns: 172.17.42.1