To discuss integrating autoscaling within both Heat and Senlin, in terms of current status, actions, improvement, design plan, and long-term goal.
Also, collect feedback from users/ops if any.
Etherpad for collect any information: https://etherpad.openstack.org/p/autoscaling-integration-and-feedback
Moderators:
* Rico Lin
* Duc Truong
IMO the biggest issues we got now are we got users using autoscaling in both services, appears there is a lot of duplicated effort, and some great enhancement didn't exist in another service. As a long-term goal (from the beginning), we should try to join development to sync functionality, and move users to use Senlin for autoscaling. So we should start to review this goal, or at least we should try to discuss how can we help users without break or enforce anything.
What will be great if we can build common library cross projects, and use that common library in both projects, make sure we have all improvement implemented in that library, finally to use Senlin from that from that library call in Heat autoscaling group. And in long-term, we gonna let all user use more general way instead of multiple ways but generate huge confusing for users. Also would benefit from both teams to start to think about how they can modulize those functionalities for easier integration in the future.
From some Heat PTG sessions, we keep bring out ideas on how can we improve current solutions for Autoscaling. We should start to talk about will it make sense if we combine all group resources into one, and inherit from it for other resources (ideally gonna deprecate rest resource types). Like we can do Batch create/delete in Resource Group, but not in ASG. We definitely got some unsynchronized works inner Heat, and cross Heat and Senlin.
