> >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.

Agreed. In an ideal world, we can transparently transplant the "scaling
group" resource implementation onto something (e.g. a library or an
interface). This sounds like an option for both teams to brainstorm

- Qiming

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to