storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joaquin Menchaca <jmench...@gobalto.com>
Subject Re: Storm UI generated logviewer links problematic
Date Wed, 07 Sep 2016 22:34:44 GMT
Thank you so much... That is awesome! :)

On Tue, Sep 6, 2016 at 12:13 PM, P. Taylor Goetz <ptgoetz@gmail.com> wrote:

> You can override DNS by setting storm.local.hostname in the config yaml on
> each node. Use the public IP/hostname and that should fix your problem.
>
> -Taylor
>
>
> On Sep 6, 2016, at 2:47 PM, Joaquin Menchaca <jmenchaca@gobalto.com>
> wrote:
>
> This is a big issue to how *storm ui* generates the URLs to access *storm
> logviewer*.  I need to have some control to how storm ui generates the
> links, such as using routes or custom name to represent the supervisors.
>
> In my *use case*: 1) secure VPC, only accessible through 22 from admin
> VPC, 2) storm ui available through ELB which is secured to only use public
> DNS, 3) internal DNS different that public DNS.
>
> As I understand, storm ui fetches the supervisor names from zookeeper, and
> supervisors register to zookeeper using some name it generates (hostname?
> reverse DNS lookup?)
>
> The problem is that the DNS names are not usable, even if I park a
> reverse-proxy, I cannot route to URLs that ONLY make sense to internal DNS.
>
>
>


-- 

是故勝兵先勝而後求戰,敗兵先戰而後求勝。

Mime
View raw message