Hi folks. I have just started working on the blueprint about static datasource config format[1]. The planned working items are as following.
1. create new datasource `static` to parse new configuration format 2. parse old configuration format in `static` with a proxy to existing `static_physical` module 3. remove `static_physical` datasource and print deprecation warning in `static` 4. merge common logic with scenario template evaluator Requesting for comments. P.S. I chose the name `static` since it is actually not limited to physical entities. Virtual entities can also be described in `static` file if there is no dynamic source. [1]: https://blueprints.launchpad.net/vitrage/+spec/static-datasource-config-format -- Yujun
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
