+1 on Non-routable IP idea. My preference is to start in Hadoop-common to
minimize the scope and incrementally improve. However, this will be
incompatible change for initial user experience on public cloud. What would be
the right release vehicle for this work (3.2+ or 4.x)?
Regards,
Eric
On 7/5/18, 2:33 PM, "larry mccay" <lmc...@apache.org> wrote:
+1 from me as well.
On Thu, Jul 5, 2018 at 5:19 PM, Steve Loughran <ste...@hortonworks.com>
wrote:
>
>
> > On 5 Jul 2018, at 23:15, Anu Engineer <aengin...@hortonworks.com> wrote:
> >
> > +1, on the Non-Routable Idea. We like it so much that we added it to the
> Ozone roadmap.
> > https://issues.apache.org/jira/browse/HDDS-231
> >
> > If there is consensus on bringing this to Hadoop in general, we can
> build this feature in common.
> >
> > --Anu
> >
>
>
> +1 to out the box, everywhere. Web UIs included
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
