Yohann commented on METRON-409:
IMHO, the ability to deploy the full Metron stack on an isolated network is a
For example, the "[French Networks and Information Security
has published a [requirements reference
applicable to a security incident detection service provider with the following
bq. _IV.3.11. a)_ The service provider *can* implement an internal relay
station connected to a dedicated Internet gateway to enable the downloading of
updates of the security incident detection service’s devices.
bq. _IV.3.11. b)_ The service provider *must* conduct a manual, *offline
update* of the security incident detection service’s devices that cannot be
updated via a relay station.
> 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