This thread, others before, and some of my own experiences lead me to
believe we need to make site-to-site status information more obvious.
It isn't easy to know whether site to site is configured for a given
node/cluster and whether it is actually working and whether it is
secure.  Perhaps we should make a JIRA to add a status page showing
the status of key items like this so users can get a nice 'Green
checkbox' that it is on and good or a 'red x' that is off or not
configured.

On Tue, Apr 28, 2015 at 11:58 AM, Mark Payne <[email protected]> wrote:
> Anup,
>
> So whether you are sending to a cluster or a standalone NiFi it should work
> exactly the same way. But it is important that your cluster manager also has
> the "remote.input.socket.port" property set. Otherwise it should all work
> the same.
>
> If you want to run secure, I'd recommend you go through the Admin Guide to
> run securely. You can get to that in the help menu of the app.
>
> Beyond that, whenever you try to connect to the secure instance via
> site-to-site, it will automatically request access to the flow. Then you'll
> go to the Users page and give the requestor the "NiFi" role. Then you can
> right-click and configure a port and go to "Access Controls" and specify
> which users can interact with that port.
>
> Thanks
> -Mark
>
> ------ Original Message ------
> From: "anup s" <[email protected]>
> To: [email protected]
> Sent: 4/28/2015 11:25:37 AM
> Subject: RE: configuring site-to-site
>
>> Its http, but want to move to https. Actually, the second machine I had
>> mentioned is configured as a cluster and I am providing enabling the secure
>> ports In the NCM.
>>
>> I tried configuring another nifi-instance in a non-clustered mode and
>> called the RPG group. This time it worked. :)
>>
>> I probably need to set the input ports for cluster mode and that should
>> work. Please let me know if there are additional things to do.
>> Also, it would be great if you could let me know the process to make it
>> secure.
>>
>> Thanks again.
>>
>> From: Mark Payne [via Apache NiFi (incubating) Developer List]
>> [mailto:[email protected]]
>> Sent: Tuesday, April 28, 2015 8:31 PM
>> To: Sethuram, Anup
>> Subject: Re: configuring site-to-site
>>
>> OK. So a couple of more questions then:
>>
>> Is the NiFi instance that you're trying to connect to secure (i.e., http
>> or https)? If you are running https then you will need to allow the
>> other instance to access the port. Will go into that a bit more if
>> that's the case. If http, then it's not an issue.
>>
>> The Input Port that you created on the instance that you're trying to
>> send to - did you create it on the root group, or did you create it
>> within a sub-group?
>>
>> Were you able to find the 'refresh' button in the context menu?
>>
>>
>>
>> ------ Original Message ------
>> From: "anup s" <[hidden
>> email]</user/SendEmail.jtp?type=node&node=1268&i=0>>
>> To: [hidden email]</user/SendEmail.jtp?type=node&node=1268&i=1>
>> Sent: 4/28/2015 10:55:29 AM
>> Subject: RE: configuring site-to-site
>>
>>> Mark,
>>>    Yes, That works. But I don't see the ports appearing in RPG ports.
>>>
>>> From: Mark Payne [via Apache NiFi (incubating) Developer List]
>>> [mailto:[hidden email]</user/SendEmail.jtp?type=node&node=1268&i=2>]
>>> Sent: Tuesday, April 28, 2015 8:23 PM
>>> To: Sethuram, Anup
>>> Subject: Re: configuring site-to-site
>>>
>>> Anup,
>>>
>>> If you right-click on the RPG and click "Go to" does it take you to the
>>> other instance?
>>>
>>> ------ Original Message ------
>>> From: "anup s" <[hidden
>>> email]</user/SendEmail.jtp?type=node&node=1266&i=0>>
>>> To: [hidden email]</user/SendEmail.jtp?type=node&node=1266&i=1>
>>> Sent: 4/28/2015 10:49:09 AM
>>> Subject: Re: configuring site-to-site
>>>
>>>> Hi Corey,
>>>>      I don't see any input ports been shown in Remote Process Group
>>>> Ports
>>>> :(
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>>
>>>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/configuring-site-to-site-tp1253p1265.html
>>>> Sent from the Apache NiFi (incubating) Developer List mailing list
>>>> archive at Nabble.com.
>>>
>>>
>>> ________________________________
>>> If you reply to this email, your message will be added to the
>>> discussion below:
>>>
>>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/configuring-site-to-site-tp1253p1266.html
>>> To unsubscribe from configuring site-to-site, click
>>> here<
>>>
>>> NAML<http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>>
>>> ________________________________
>>> The information contained in this message may be confidential and
>>> legally protected under applicable law. The message is intended solely
>>> for the addressee(s). If you are not the intended recipient, you are
>>> hereby notified that any use, forwarding, dissemination, or
>>> reproduction of this message is strictly prohibited and may be
>>> unlawful. If you are not the intended recipient, please contact the
>>> sender by return e-mail and destroy all copies of the original message.
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>>
>>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/configuring-site-to-site-tp1253p1267.html
>>> Sent from the Apache NiFi (incubating) Developer List mailing list
>>> archive at Nabble.com.
>>
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/configuring-site-to-site-tp1253p1268.html
>> To unsubscribe from configuring site-to-site, click
>> here<http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1253&code=YW51cC5zZXRodXJhbUBwaGlsaXBzLmNvbXwxMjUzfDEwMjY1NTEyNjc=>.
>>
>> NAML<http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>> ________________________________
>> The information contained in this message may be confidential and legally
>> protected under applicable law. The message is intended solely for the
>> addressee(s). If you are not the intended recipient, you are hereby notified
>> that any use, forwarding, dissemination, or reproduction of this message is
>> strictly prohibited and may be unlawful. If you are not the intended
>> recipient, please contact the sender by return e-mail and destroy all copies
>> of the original message.
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/configuring-site-to-site-tp1253p1271.html
>> Sent from the Apache NiFi (incubating) Developer List mailing list archive
>> at Nabble.com.

Reply via email to