drop rpc functionality

[gordon chung]

the collector supports udp, rpc and notifier publishing. i'm not sure rpc offers anything more than notifier. it is significantly slower... do we need to keep it around?

[Chris Dent (cdent)]

I had a vague impression that rpc had a strong reliability guarantee? If not then yes we should totally kill it but I guess we'll need a deprecation plan.

[Julien Danjou (jdanjou)]

We need to remove it, but we need to deprecate it because I know people are using it with their own collector (yeah even if it was a bad idea).

[gordon chung (chungg)]

i'm not sure it offers any more reliability vs queues. it's really only intended when publisher expects a response, which we don't need.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/211304

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/211304
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=a27643a75ff985c0d61f3c10ad6cdce109845bf9
Submitter: Jenkins
Branch: master

commit a27643a75ff985c0d61f3c10ad6cdce109845bf9
Author: gordon chung <email address hidden>
Date: Mon Aug 10 15:28:29 2015 -0400

    start rpc deprecation

    we switch to work queues in Juno and made it the default rather
    than rpc. the main advantage of using RPC is it offers callback
    functionality at the expense of performance. we don't need callback
    for our use cases so it's best to stop supporting rpc and leave just
    udp and queues in our collector.

    Change-Id: Ia02421ae09cdf27998ce76a99170100f36595f71
    Related-Bug: #1479820