Use containerized mongodb in scenario002-multinode-containers

The containerized mongodb service was removed from the default service
list from 'environments/docker.yaml' in
Ie09ce2a52128eef157e4d768c1c4776fc49f2324. This commit re-enable the
containerized mongodb in scenario002-multinode-containers.

Change-Id: I57958c94022ccac3ec2ebf7c9438b9e47cbad337
Closes-Bug: #1715391
(cherry picked from commit 13d2bdf41ca3b726acff0b94dae6d394dab4af23)

diff --git a/ci/environments/scenario002-multinode-containers.yaml b/ci/environments/scenario002-multinode-containers.yaml
index f1dc268..0ca67d0 100644 (file)
--- a/ci/environments/scenario002-multinode-containers.yaml
+++ b/ci/environments/scenario002-multinode-containers.yaml
@@ -9,6 +9,7 @@ resource_registry:
   OS::TripleO::Services::BarbicanApi: ../../docker/services/barbican-api.yaml
   OS::TripleO::Services::Zaqar: ../../docker/services/zaqar.yaml
   OS::TripleO::Services::Ec2Api: ../../docker/services/ec2-api.yaml
+  OS::TripleO::Services::MongoDb: ../../docker/services/database/mongodb.yaml
   # NOTE: This is needed because of upgrades from Ocata to Pike. We
   # deploy the initial environment with Ocata templates, and
   # overcloud-resource-registry.yaml there doesn't have this Docker