[jira] [Commented] (NIFI-3695) Create Node Manager & Notification Utilities

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966457#comment-15966457 ] 

ASF GitHub Bot commented on NIFI-3695:
--------------------------------------

GitHub user YolandaMDavis opened a pull request:

    https://github.com/apache/nifi/pull/1669

    NIFI-3695 - created the nifi admin toolkit which includes shell scrip…

    …ts and classes to support notification and basic node management in standalone and clustered nifi.
    
    Documentation
    [Admin Toolkit for NiFi.docx](https://github.com/apache/nifi/files/917612/Admin.Toolkit.for.NiFi.docx)
     and use case information is attached
    
    
    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [X] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [X] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [X] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [X] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/YolandaMDavis/nifi NIFI-3695

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1669.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1669
    
----
commit c6e66279d0d7e9b803f51ce9715262b51e25d8d1
Author: Yolanda M. Davis <yo...@gmail.com>
Date:   2017-02-07T15:28:15Z

    NIFI-3695 - created the nifi admin toolkit which includes shell scripts and classes to support notification and basic node management in standalone and clustered nifi.

----


> Create Node Manager & Notification Utilities
> --------------------------------------------
>
>                 Key: NIFI-3695
>                 URL: https://issues.apache.org/jira/browse/NIFI-3695
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Tools and Build
>            Reporter: Yolanda M. Davis
>            Assignee: Yolanda M. Davis
>
> The node manager utility should allow system administrators to connect, disconnect or remove a node from a cluster on the command line.  If a node is not part of a cluster an error message should display if node is not part of a cluster.  If a node is disconnected from a cluster and needs to be connected or removed from that cluster the tool should support receiving a list of urls to connected nodes which can be used to send the required command to the active cluster. 
> The notification utility should allow administrators to send messages as bulletins to the NiFi with levels of INFO, WARN or ERROR.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)