From ea00cd3be5b11e2d1db051e711b7421ddc4511f8 Mon Sep 17 00:00:00 2001 From: gord chung Date: Fri, 8 Dec 2017 16:47:20 +0000 Subject: [PATCH] remove kafka publisher it's been removed. Change-Id: I8e88573e5526b663d3f25055d6cfad534e3fef5c --- doc/source/admin/telemetry-data-pipelines.rst | 29 ------------------- 1 file changed, 29 deletions(-) diff --git a/doc/source/admin/telemetry-data-pipelines.rst b/doc/source/admin/telemetry-data-pipelines.rst index 7f40458c91..91c519a02b 100644 --- a/doc/source/admin/telemetry-data-pipelines.rst +++ b/doc/source/admin/telemetry-data-pipelines.rst @@ -516,32 +516,3 @@ specified. A sample ``publishers`` section in the - panko:// - udp://10.0.0.2:1234 - notifier://?policy=drop&max_queue_length=512&topic=custom_target - - -Deprecated publishers ---------------------- - -The following publishers are deprecated as of Ocata and may be removed in -subsequent releases. - -kafka -````` - -.. note:: - - We recommened you use oslo.messaging if possible as it provides consistent - OpenStack API. - -The ``kafka`` publisher can be specified in the form of: -``kafka://kafka_broker_ip: kafka_broker_port?topic=kafka_topic -&option1=value1``. - -This publisher sends metering data to a kafka broker. The kafka publisher -offers similar options as ``notifier`` publisher. - -.. note:: - - If the topic parameter is missing, this publisher brings out - metering data under a topic name, ``ceilometer``. When the port - number is not specified, this publisher uses 9092 as the - broker's port.