Hi, During previous OpenStack releases, projects using mongodb as backend (as telemetry or zaqar) have moved to other technologies for data persistence and mongo is not longer the default or preferred backend. In this cycle (Queens), mongodb packages will be retired from RDO repositories under the assumption that users have implemented any of the alternatives for each affected service (or are in the process of doing it). This will happen in next weeks and will not affect previous releases. If you have any question or you think that mongo should be maintained in RDO, please feel free to let us know in this thread or reach us in #rdo so that we can consider all implications of this decision. Best regards, Alfredo _______________________________________________ dev mailing list dev(a)lists.rdoproject.org http://lists.rdoproject.org/mailman/listinfo/dev To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org

On Tue, Nov 28, 2017 at 1:36 AM, Donny Davis <donny(a)fortnebula.com&gt; wrote: > Isn’t tripleo still using mongo? It's been disabled by default for a while[1] but a couple of places still reference it, most notably it's still the default backend for Zaqar in the overcloud. Work is ongoing to switch that to redis, and I reached out to therve who is working on that to check the status, he says: "Technically it's still the default for Zaqar, but we do support Swift and Redis now, and Redis should probably be the new default. We don't require Mongo anymore (and never really supported it really well). so it can be dropped." Also note that Zaqar is only tested in CI with swift as a backend[2], so I'd suggest we make the switch to redis as the default then ensure it is tested in CI, and deprecate then remove support for Mongo from TripleO.

Thanks! Steve [1] https://review.openstack.org/#/c/466265/ [2] https://github.com/openstack/tripleo-heat-templates/blob/ master/ci/environments/scenario002-multinode-containers.yaml#L88