Remove iscsid from TLS everywhere docker environment
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Thu, 17 Aug 2017 08:04:10 +0000 (08:04 +0000)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Thu, 17 Aug 2017 08:04:10 +0000 (08:04 +0000)
Since nova-compute is not containerized with TLS yet, using containerized
iscsid causes errors when trying to spawn a VM with a volume. Since
the path is different in this case.

I will re-add iscsid to this environment once nova-compute is
containerized with TLS.

bp tls-via-certmonger-containers

Change-Id: Ida87b187e56ae852c5a4ef6f78cc04a0870fe3f4

environments/docker-services-tls-everywhere.yaml

index 49d02e6..390cad2 100644 (file)
@@ -26,7 +26,6 @@ resource_registry:
   OS::TripleO::Services::HeatApi: ../docker/services/heat-api.yaml
   OS::TripleO::Services::HeatApiCfn: ../docker/services/heat-api-cfn.yaml
   OS::TripleO::Services::HeatEngine: ../docker/services/heat-engine.yaml
-  OS::TripleO::Services::Iscsid: ../docker/services/iscsid.yaml
   OS::TripleO::Services::Keystone: ../docker/services/keystone.yaml
   OS::TripleO::Services::Memcached: ../docker/services/memcached.yaml
   OS::TripleO::Services::NeutronApi: ../docker/services/neutron-api.yaml