metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Allen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METRON-409) Document requred network/proxy connectivity
Date Thu, 08 Sep 2016 20:38:20 GMT

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

Nick Allen commented on METRON-409:
-----------------------------------


> Even better would be a method to pull down all the required packages all at once to be
added to an internally-hosted repo.

I had done exactly that at one point and it was working.  I was able to do deployments on
an isolated network.  At the time, it wasn't something that we wanted to support long term.
 I still have the code in a branch.  Of course the branch is ancient by now.  The merge conflicts
would give me nightmares.

https://issues.apache.org/jira/browse/METRON-187

https://github.com/nickwallen/incubator-metron/tree/METRON-187



> Document requred network/proxy connectivity
> -------------------------------------------
>
>                 Key: METRON-409
>                 URL: https://issues.apache.org/jira/browse/METRON-409
>             Project: Metron
>          Issue Type: Wish
>            Reporter: Jon Zeolla
>            Priority: Minor
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> I'm doing a physical install on HDP 2.4 behind a corporate proxy and the network connectivity
is both hard to nail down exactly and somewhat lengthy.  For future installs it would be nice
if there was a piece of documentation which listed the destinations Metron needs to go to
for the various packages, and a method to specify how to use the proxies in one place.  I
had to add my proxies in metron_install.yml, set no_proxy for all members of the cluster,
and also handle some one-off proxy settings (such as npm config proxy <proxy details>
on the kibana box, for instance) manually.  
> Even better would be a method to pull down all the required packages all at once to be
added to an internally-hosted repo.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message