[all][ptl][heat][senlin][magnum]New SIG for Autoscaling? plus, Session Summary: Autoscaling Integration, improvement, and feedback
joseph.davis at suse.com
Thu Nov 29 19:30:00 UTC 2018
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. :)
On Wed, Nov 28, 2018 at 4:00 AM Rico Lin<rico.lin.guanyu at gmail.com> wrote:
> I gonna use this ML to give a summary of the forum  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
>  https://etherpad.openstack.org/p/autoscaling-integration-and-feedback
On Thu, 29 Nov 2018 09:32:17 "Bedyk, Witold"<witold.bedyk at est.fujitsu.com> wrote:
> Hi Rico,
> Thanks for this initiative. I think the SIG could be a good channel to coordinate this work across the projects.
> From Monasca perspective, I would like to make sure that we provide all necessary monitoring data to cover the defined use cases and that Monasca alarms can be seamlessly consumed by the integrated services.
> We’re also interested in contributing documentation in the central place.
> I’m sure operators will be thankful for having a channel for providing dedicated feedback.
More information about the openstack-discuss