Disable Sahara in scenario003-standalone
Sahara service is deprecated in TripleO and won't be tested anymore to align with what is delivered downstream. In the new container image tooling, we don't ship sahara images simply because we don't have users and won't continue to support it's deployment in the future. Change-Id: If1c621b45718475578dca390c45c0e23d1f3d7bc
This commit is contained in:
parent
e4785b3790
commit
03285912fc
|
@ -6,8 +6,6 @@ resource_registry:
|
|||
OS::TripleO::Services::SwiftProxy: OS::Heat::None
|
||||
OS::TripleO::Services::SwiftStorage: OS::Heat::None
|
||||
OS::TripleO::Services::SwiftRingBuilder: OS::Heat::None
|
||||
OS::TripleO::Services::SaharaApi: ../../deployment/deprecated/sahara/sahara-api-container-puppet.yaml
|
||||
OS::TripleO::Services::SaharaEngine: ../../deployment/deprecated/sahara/sahara-engine-container-puppet.yaml
|
||||
OS::TripleO::Services::MistralApi: ../../deployment/mistral/mistral-api-container-puppet.yaml
|
||||
OS::TripleO::Services::MistralEngine: ../../deployment/mistral/mistral-engine-container-puppet.yaml
|
||||
OS::TripleO::Services::MistralExecutor: ../../deployment/mistral/mistral-executor-container-puppet.yaml
|
||||
|
|
Loading…
Reference in New Issue