Hi Teams, In Pike release QA team has copied the Tempest scenario manager on plugin side to refactor the same and to avoid breaking any plugin [1]. But in many plugins, scenario manager was copied as complete and expected to shrink by each plugin as per their usage. Because scenario manager has lot of class/methods which might not be used by each plugin. Those class/method internally use many tempest interfaces which all might not be stable. Tempest is trying to make them stable interfaces for plugin. That is ongoing work from QA team since many releases. This work sometime break the scenario manager copy on plugin side. One ongoing example is to make object storage service clients as stable interfaces [2]. To avoid such issues i have started to shrink the scenario manager copy on remaining plugin side [3]. Each corresponding team is requested to merge them. Also those are needed to backport on stable branches as plugins are still in project repo. I have backported some of them for Pike [4] and project team can backport to other stable branches based on their need. Please ping us on QA channel for any clarification. ..1 http://lists.openstack.org/pipermail/openstack-dev/2017-February/112938.html ..2 https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/consistent-service-method-names ..3 https://review.openstack.org/#/q/topic:shrink-scenario-manager+(status:open+OR+status:merged) ..4 https://review.openstack.org/#/q/topic:shrink-scenario-manager-stable/pike+(status:open+OR+status:merged) -gmann