Open Stack

On 27/09/18 7:00 PM, Duc Truong wrote:
> On Thu, Sep 27, 2018 at 11:14 AM Zane Bitter <zbitter at redhat.com> wrote:
>>
>>> and we will gradually fade out the existing 'AutoScalingGroup'
>>> and related resource types in Heat.
>>
>> That's almost impossible to do without breaking existing users.
> 
> One approach would be to switch the underlying Heat AutoScalingGroup
> implementation to use Senlin and then deprecate the AutoScalingGroup
> resource type in favor of the Senlin resource type over several
> cycles. 

The hard part (or one hard part, at least) of that is migrating the 
existing data.

> Not saying that this is the definitive solution, but it is
> worth discussing as an option since this follows a path other projects
> have taken (e.g. nova-volume extraction into cinder).

+1, *definitely* worth discussing.

> A prerequisite to this approach would probably require Heat to create
> the so-called common library to house the autoscaling code.  Then
> Senlin would need to achieve feature parity against this autoscaling
> library before the switch could happen.
> 
>>
>> Clearly there are _some_ parts that could in principle be shared. (I
>> added some comments to the etherpad to clarify what I think Rico was
>> referring to.)
>>
>> It seems to me that there's value in discussing it together rather than
>> just working completely independently, even if the outcome of that
>> discussion is that
> 
> +1.  The outcome of any discussion will be beneficial not only to the
> teams but also the operators and users.
> 
> Regards,
> 
> Duc (dtruong)
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>