scenario002/container: run Barbican non-containerized
authorEmilien Macchi <emilien@redhat.com>
Tue, 15 Aug 2017 03:46:10 +0000 (20:46 -0700)
committerEmilien Macchi <emilien@redhat.com>
Thu, 17 Aug 2017 05:24:42 +0000 (05:24 +0000)
... until https://review.openstack.org/#/c/474327 is merged.
In the meantime, let's test the scenario with Barbican like before.

Depends-On: Ib5c99482f62397fc5fb79a9dc537dfb06ee7f4df
Change-Id: Ia96736ad3ddabd33c5ee4518a3f63bafeffcf391

ci/environments/scenario002-multinode-containers.yaml

index d300f77..a4752c4 100644 (file)
@@ -8,6 +8,7 @@ resource_registry:
   OS::TripleO::Compute::Net::SoftwareConfig: ../common/net-config-multinode.yaml
   # TODO: Barbican is not yet containerized: https://review.openstack.org/#/c/474327
   # OS::TripleO::Services::BarbicanApi: ../../docker/services/barbican-api.yaml
+  OS::TripleO::Services::BarbicanApi: ../../puppet/services/barbican-api.yaml
   OS::TripleO::Services::Zaqar: ../../docker/services/zaqar.yaml
   OS::TripleO::Services::Ec2Api: ../../docker/services/ec2-api.yaml
   # NOTE: This is needed because of upgrades from Ocata to Pike. We