From ca7bfdac3553881d82e2fe576fbd0172b2c1a21a Mon Sep 17 00:00:00 2001 From: Yujun Zhang Date: Tue, 22 Nov 2016 13:47:15 +0800 Subject: [PATCH] blueprint static-datasource-configuration - clarification on backward compatibility Change-Id: I3ee3103535760ae0415d034c640bfafdf4b4cbf3 --- specs/ocata/static-datasource-configuration.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/specs/ocata/static-datasource-configuration.rst b/specs/ocata/static-datasource-configuration.rst index e349bde..154940d 100644 --- a/specs/ocata/static-datasource-configuration.rst +++ b/specs/ocata/static-datasource-configuration.rst @@ -78,6 +78,18 @@ evaluator template. Discover entities from the static data source template. +For backward compatibility, static data source will take over the control of the +default configuration folder ``/etc/vitrage/static_datasource`` which was used +by static physical datasource. + +Both legacy format and new format will be placed in the same folder. static +datasource parse the file and check the existence of ``meta`` to decide which +engine to use. If not found, proxy the job to static physical datasource and +print a deprecation warning. + +Static physical datasource will be disabled by default and throws exception if +running standalone. + Alternatives ------------