-
Notifications
You must be signed in to change notification settings - Fork 422
Upgraded to Mongo 3.0 #60
Conversation
Release Notes # Destroy all containers
make devstack.reset
# Remove the Mongo data volume
docker volume rm devstack_mongo_data
# Re-create the demo course
make devstack.provision |
@edx/devops please review FYI @edx/ecommerce |
docker-compose.yml
Outdated
container_name: edx.devstack.mongo | ||
image: mongo:2.6.5 | ||
image: mongo:3.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@clintonb is this consistent with the version we run in production?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. See #52.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good news is that when we get to 3.2/3.4 you won't have to specify wiredTiger
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. We're already using mongo:3.0.14 in the forums travis tests (My only question is whether you should pin to the specific subversion we use, but not a blocker, especially since 3.0 is mostly in maintenance now).
docker-compose.yml
Outdated
container_name: edx.devstack.mongo | ||
image: mongo:2.6.5 | ||
image: mongo:3.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good news is that when we get to 3.2/3.4 you won't have to specify wiredTiger
Fixes #52
Pinned to |
Fixes #52