Github user apiri commented on a diff in the pull request:

    https://github.com/apache/nifi-minifi-cpp/pull/424#discussion_r226762332
  
    --- Diff: OPS.md ---
    @@ -0,0 +1,95 @@
    +<!--
    +  Licensed to the Apache Software Foundation (ASF) under one or more
    +  contributor license agreements.  See the NOTICE file distributed with
    +  this work for additional information regarding copyright ownership.
    +  The ASF licenses this file to You under the Apache License, Version 2.0
    +  (the "License"); you may not use this file except in compliance with
    +  the License.  You may obtain a copy of the License at
    +      http://www.apache.org/licenses/LICENSE-2.0
    +  Unless required by applicable law or agreed to in writing, software
    +  distributed under the License is distributed on an "AS IS" BASIS,
    +  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +  See the License for the specific language governing permissions and
    +  limitations under the License.
    +-->
    +
    +# Apache NiFi - MiNiFi - Operations Readme.
    +
    +
    +This readme defines operational commands for managaging instances.
    +
    +## Table of Contents
    +
    +- [Description](#description)
    +- [Managing](#managing-minifi)
    +  - [Commands](#commands)
    +
    +## Description
    +
    +Apache NiFi MiNiFI C++ can can be managed through our [C2 
protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal)
 
    +or through a local interface called the MiNiFi Controller
    +
    +## Managing MiNiFi
    +
    +The MiNiFi controller is an executable in the bin directory that can be 
used to control the MiNiFi C++ agent while it runs -- utilizing the [Command 
and Control 
Protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal).
 Currently the controller will let you stop subcomponents within a running 
instance, clear queues, get the status of queues, and update the flow for a 
warm re-deploy.
    +
    +The minificontroller can track a single MiNiFi C++ agent through the use 
of three options. Port is required.
    +The hostname is not and will default to localhost. Additionally, 
controller.socket.local.any.interface allows
    +you to bind to any address when using localhost. Otherwise, we will bind 
only to the loopback adapter so only
    +minificontroller on the local host can control the agent:
    +
    +   $ controller.socket.host=localhost
    +   $ controller.socket.port=9998
    +   $ controller.socket.local.any.interface=true/false ( default false)
    --- End diff --
    
    parentheses spacing


---

Reply via email to