Open Stack

Hi All,

As discussed in the last meeting, here is the ML thead to gather more
feedback on this.

Background:

Heat support for AWS CloudWatch compatible API (a very minimalistic
implementation, primarily used for metric data collection for autoscaling,
before the telemetry services in OpenStack), has been deprecated since
Havana cycle (may be before that?).  We now have a global alias[1] for
AWS::CloudWatch::Alarm to use OS::Aodh::Alarm instead.  However, the
ability to push metrics to ceilometer via heat, using a pre-signed url for
CloudWatch api endpoint, is still supported for backward compatibility.
heat-cfntools/cfn-push-stats tool is mainly used from the instances/vms for
this.

What we plan to do?

We think that CloudWatch api  and related code base has been in heat tree
without any change for the sole reason above and possibly it's time to
remove them completely. However, we may not have an alternate way to
continue providing backward compatibility to users.

What would be the impact?

- Users using AWS::CloudWatch::Alarm and pushing metric data from instances
using cfn-push-stats would not be able to do so. Templates with these would
not work any more.

- AWS::ElasticLoadBalancing::LoadBalancer[2] resource which uses
AWS::CloudWatch::Alarm and cfn-push-stats would not work anymore. We
probably have to remove this resource too?

Though it seems like a big change, the general opinion is that there would
not be many users still using them and hence very little risk in removing
CloudWatch support completely this cycle.

If you think otherwise please let us know:)


[1] https://git.openstack.org/cgit/openstack/heat/tree/etc/
heat/environment.d/default.yaml#n6
[2]
https://git.openstack.org/cgit/openstack/heat/tree/heat/engine/resources/aws/lb/loadbalancer.py#n640

Regards,
Rabi Mishra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171004/be098fe3/attachment.html>