Update to Mongo 3.0 about devstack HOT 4 CLOSED

@edx/devops is there anything we should be aware of regarding Mongo configuration? Is there certain functionality/configuration that only makes sense in production, and should be avoided for development?

from devstack.

No, I don't think so. Ideally, we would run three in all situations so that stepdowns and such could be tested in local environments. There might be other reasons why that doesn't make sense, in which case the single mongo should bi a replica set with one member and require auth to login.

from devstack.

The only other thing is you likely want the small journal setting, otherwise it'll try to create a multiple GB journal file that it only uses like 4k of.

from devstack.

I'm not certain what the performance gains are for devstack; but, we need to eek out every gain we can to make this devstack's speed comparable to Vagrant.

from devstack.