[Bugs] [Bug 1334044] [RFE] Eventing for Gluster

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1334044



--- Comment #17 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14248 committed in master by Jeff Darcy
(jdarcy at redhat.com) 
------
commit 5ed781ecf531b7916e51c174426e222dab717fb8
Author: Aravinda VK <avishwan at redhat.com>
Date:   Thu May 5 18:34:41 2016 +0530

    eventsapi: Gluster Eventing Feature implementation

    [Depends on http://review.gluster.org/14627]

    Design is available in `glusterfs-specs`, A change from the design
    is support of webhook instead of Websockets as discussed in the design

    http://review.gluster.org/13115

    Since Websocket support depends on REST APIs, I will add Websocket support
    once REST APIs patch gets merged

    Usage:
    Run following command to start/stop Eventsapi server in all Peers,
    which will collect the notifications from any Gluster daemon and emits
    to configured client.

        gluster-eventsapi start|stop|restart|reload

    Status of running services can be checked using,

        gluster-eventsapi status

    Events listener is a HTTP(S) server which listens to events emited by
    the Gluster. Create a HTTP Server to listen on POST and register that
    URL using,

        gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]

    For example, if HTTP Server running in `http://192.168.122.188:9000`
    then add that URL using,

        gluster-eventsapi webhook-add http://192.168.122.188:9000

    If it expects a Token then specify it using `--bearer-token` or `-t`

    We can also test Webhook if all peer nodes can send message or not
    using,

        gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]

    Configurations can be viewed/updated using,

        gluster-eventsapi config-get [--name]
        gluster-eventsapi config-set <NAME> <VALUE>
        gluster-eventsapi config-reset <NAME|all>

    If any one peer node was down during config-set/reset or webhook
    modifications, Run sync command from good node when a peer node comes
    back. Automatic update is not yet implemented.

        gluster-eventsapi sync

    Basic Events Client(HTTP Server) is included with the code, Start
    running the client with required port and start listening to the
    events.

        /usr/share/glusterfs/scripts/eventsdash.py --port 8080

    Default port is 9000, if no port is specified, once it started running
    then configure gluster-eventsapi to send events to that client.

    Eventsapi Client can be outside of the Cluster, it can be run event on
    Windows. But only requirement is the client URL should be accessible
    by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)

    Events implemented with this patch,
    - Volume Create
    - Volume Start
    - Volume Stop
    - Volume Delete
    - Peer Attach
    - Peer Detach

    It is easy to add/support more events, since it touches Gluster cmd
    code and to avoid merge conflicts I will add support for more events
    once this patch merges.

    BUG: 1334044
    Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
    Signed-off-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-on: http://review.gluster.org/14248
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=DnaapCVlNS&a=cc_unsubscribe