OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 month ago|
|doc/source||2 years ago|
|lpmqtt||2 years ago|
|.gitignore||2 years ago|
|.gitreview||1 month ago|
|.testr.conf||2 years ago|
|CONTRIBUTING.rst||2 years ago|
|LICENSE||2 years ago|
|README.rst||2 years ago|
|requirements.txt||2 years ago|
|setup.cfg||2 years ago|
|setup.py||2 years ago|
|test-requirements.txt||2 years ago|
|tox.ini||2 years ago|
lpmqtt, like its name implies, is a tool for publish a launchpad event stream into MQTT. It will publish all the capture events from the lp emails over imap and publish them to MQTT
lpmqtt will push launchpad events to topics broken by project and event type. The formula used is:
<base topic>/<project>/<bugs, blueprints, or other event type>/<bug number>
However only the base topic is a guaranteed field. Depending on the emails sent by launchpad some of the other fields may not be present. In those cases the topic will start from the base topic and will use fields moving towards the right until one is missing.
lpmqtt only runs in the foreground and logs all log messages to STDOUT. It takes one argument, the config file (there is no default path) which is required. For example:
% lpmqtt /etc/lpmqtt.conf
will run lpmqtt.
There are a few required pieces of information to make lpmqtt work properly. These settings are specified in the config file.
To configure lpmqtt to listen to your imap server you need to provide 3 pieces of information in the [imap] section
- hostname - The hostname for the imap server to connect to
- username - The username to connect with
- password - The password to use
There are also a number of optional settings you can use depending on the configuration of the imap server you're connecting to:
- use_ssl - Set this to True to establish an imaps connection with ssl
- folder - Specify a mailbox/folder to watch for message from launchpad.
If one is not specified INBOX will be used
- delete-old - Set this to True to have lpmqtt delete messages after it
finishes processing them. By default it will just mark them as read.
- idle-timeout - The number of seconds to use for the idle timeout
Just as with imap there are a few required options for talking to MQTT, which is the other axis of communication in lpmqtt. The options for configuring MQTT communication go in the [mqtt] section. The 2 required options are:
- hostname - The hostname for the MQTT broker
- base_topic - The base topic name to use for the gerrit events
There are also a couple optional settings for communicating with mqtt that you can set:
- port - The port to communicate to the MQTT broker on. By default this
is set to 1883, the default MQTT port. This only needs to be set if your broker uses a non-default port.
- keepalive - Used to set the keepalive time for connections to the MQTT
broker. By default this is set to 60 seconds.
- username - Used to set the auth username to connect to the MQTT broker
- password - Used to set the auth password to connect to the MQTT broker
with. A username must be set for this option to be used.