Good question :) On Fri, Oct 14, 2016, 17:07 Ryan Merriman <merrim...@gmail.com> wrote:
> Jon, > > It wasn't intentional, I ran out of time and wanted to get something out > there. I think it certainly could be open ended though. Where should the > REST API project be located? > > Ryan > > On Thu, Oct 13, 2016 at 7:32 PM, zeo...@gmail.com <zeo...@gmail.com> > wrote: > > > Along the lines of: > > • Must be deployed to a machine with adequate resources so that resource > > contention is avoided. > > • Will need network access to all other services within Metron > > > > Has there been any consideration of a "Metron Manager" node? In the old > > TP2 > > bare metal install guide > > <https://cwiki.apache.org/confluence/display/METRON/ > > Metron+Installation+on+an+Ambari-Managed+Cluster> > > it mentions a "Metron Installer," but I could see the needs for that sort > > of a system expanding to have the following roles: > > - API > > - Metron UI > > - Metron Installer/upgrades > > - Edge/Gateway Node for data loading > > - Clients > > > > Also, at the end it ends mid-sentence under "Organization within Metron," > > was that intended to be open ended? > > > > Jon > > > > On Thu, Oct 13, 2016 at 6:10 PM Ryan Merriman <merrim...@gmail.com> > wrote: > > > > > I created a Jira to track this new feature at > > > https://issues.apache.org/jira/browse/METRON-503. I also started and > > > attached an architecture doc to that Jira with some of my ideas about > how > > > we should implement it. Please feel free to review and comment or add > to > > > it. Looking forward to everyone's ideas and feedback. > > > > > > Ryan Merriman > > > > > -- > > > > Jon > > > -- Jon
