Include the URL of your launchpad blueprint:
This blueprint will migrate to use Aodh service directly for alarm resources.
Although now we can use ceilometer-client to redirect to Aodh endpoint when creating alarm resources: https://review.openstack.org/#/c/202938
But there are some reasons I believe we should to migrate to use Aodh service directly:
1. This spec proposes to use Aodh service for alarm resources. For mostly alarm resources (except OS::Ceilometer::CombinationAlarm) can compatible with the current implementation.
2. The problem is that we can’t manage the OS::Ceilometer::CombinationAlarm by Aodh client, because Aodh client does not support. The combination alarm is deprecated and disabled by default in Aodh, and the new composite rule alarm is recommended to use. So this spec proposes to deprecate OS::Ceilometer::CombinationAlarm and to add the new composite rule alarm resource plug-in named ‘OS::Aodh::CompositeAlarm’