Agreed. I also see the similarities, but I don't think there is enough overlap to cause problems, so +1 from me. My only suggestion would be to consider whether it makes sense to slightly widen the scope, since I believe Watcher operates in the very similar area of optimisation, and to me auto-scaling just sounds like one particular use case out of many different approaches to optimisation, of which Watcher covers several. So for example you could call it the "self-optimising SIG" ;-) Feel free to copy any of the self-healing SIG's structure if it helps! Ifat Afek <ifatafekn@gmail.com> wrote:
+1 for that.
I see a lot of similarities between this SIG and the self-healing SIG, although their scopes are slightly different.
In both cases, there is a need to decide when an action should be taken (based on Ceilometer, Monasca, Vitrage etc.) what action to take (healing/scaling) and how to execute it (using Heat, Senlin, Mistral, …). The main differences are the specific triggers and the actions to perform.
I think that as a first step we should document the use cases.
Ifat
On Thu, Nov 29, 2018 at 9:34 PM Joseph Davis <joseph.davis@suse.com> wrote:
I agree with Duc and Witek that this communication could be really good.
One of the first items for a new SIG would be to define the relationship with the Self-Healing SIG. The two SIGs have a lot in common but some important differences. They can both use some of the same tools and data (Heat, Monasca, Senlin, Vitrage, etc) to achieve their purpose, but Self-Healing is about recovering a cloud when something goes wrong, while Autoscaling is about adjusting resources to avoid something going wrong. Having a clear statement may help a new user or contributor understand where there interests lie and how they can be part of the group.
Writing some clear use cases will be really valuable for all the component teams to reference. It may also be of value to identify a few reference architectures or configurations to illustrate how the use cases could be addressed. I'm thinking of stories like "A cloud with Monasca and Senlin services has 20 active VMs. When Monasca recognizes the 20 VMs have hit 90% utilization each it raises an alarm and Senlin triggers the creation of 5 more VMs to meet expected loads." Plus lots of details I just skipped over. :)
joseph
On Wed, Nov 28, 2018 at 4:00 AM Rico Lin<rico.lin.guanyu@gmail.com> wrote:
I gonna use this ML to give a summary of the forum [1] and asking for feedback for the idea of new SIG.
So if you have any thoughts for the new SIG (good or bad) please share it here.
[1] https://etherpad.openstack.org/p/autoscaling-integration-and-feedback