[openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration
duc.openstack at gmail.com
Tue Sep 18 23:29:04 UTC 2018
Thanks for creating the etherpad.
I have added a question on the common library in the etherpad.
I think we can iterate on the basic proposal before the forum in
Berlin so that we can get input from developers who won't be
able to attend in person.
On Tue, Sep 18, 2018 at 11:46 AM Rico Lin <rico.lin.guanyu at gmail.com> wrote:
> cool Duc, and it's nicely started:
> I also submit the etherpad, will add you as moderator once it's selected
> (don't know why, but can't add any more now from the web).
> Please add whatever you like to that etherpad, I will try to input more
> information ASAP.
> all information will continue to be used with or without that forum.
> On Wed, Sep 19, 2018 at 12:51 AM Duc Truong <duc.openstack at gmail.com>
>> Hi Rico,
>> I'm the Senlin PTL and would be happy to have a forum discussion in
>> Berlin about the future of autoscaling.
>> Can you go ahead and start an etherpad to capture the proposed agenda
>> and discussion items? Also, feel free to submit the forum submission
>> so that we can get it on the schedule.
>> Duc (dtruong)
>> On Mon, Sep 17, 2018 at 8:28 PM Rico Lin <rico.lin.guanyu at gmail.com>
>>> *How about a forum in Berlin for discussing autoscaling integration (as
>>> a long-term goal) in OpenStack?*
>>> Hi all, as we start to discuss how can we join develop from Heat and
>>> Senlin as we originally planned when we decided to fork Senlin from Heat
>>> long time ago.
>>> 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.
>>> *As an action, I propose we have a forum in Berlin and sync up all
>>> effort from both teams to plan for idea scenario design. The forum
>>> submission  ended at 9/26.*
>>> 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
>>> Please let me know who is interesting in this idea, so we can work
>>> together and reach our goal step by step.
>>> Also please provide though if you got any concerns about this proposal.
>>>  https://www.openstack.org/summit/berlin-2018/call-for-presentations
>>> May The Force of OpenStack Be With You,
>>> *Rico Lin*irc: ricolin
>>> OpenStack Development Mailing List (not for usage questions)
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> May The Force of OpenStack Be With You,
> *Rico Lin*irc: ricolin
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev