metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Merriman <>
Subject Re: [DISCUSS] Metron Management UI
Date Wed, 01 Feb 2017 15:18:02 GMT
Jon, I've done my best to keep this UI in sync with the API PR so you can
play around with it now if you want.  There are 2 different versions of the
UI:  one without the Blockly editor ( and one with
(  The Blockly
editor feature contains a significant amount of code so we decide to keep
it in it's own branch so reviewing will be easier.

If you are familiar with the javascript ecosystem it's not hard to start it
up but some instructions will definitely help.  I will add a README to make
this easier but here's a quick summary:

Start up the Docker environment in metron-docker
Set the "" property in
to match the IP address of your Docker machine
Run with spring active
profiles set to "docker,dev"
Navigate to metron-interface/metron-config and run "npm install"
Start the UI with "metron-config/scripts/"

We're still working on a seamless install process but this should work in
the meantime.  Feel free to reach out if you need help getting it going.
As for feedback, I wouldn't limit it to what the API currently provides the
API PR.  We can add services as needed.


On Tue, Jan 31, 2017 at 7:49 PM, <> wrote:

> First off - this is an awesome first take at a management UI and I'm
> looking forward to messing around with it.  Other than skimming some of the
> dialogue as it comes in I have not been keeping up with the API PR.  Should
> I be able to assume that the UI PR is broken until the API is merged and
> the UI can be updated for any changes?  I have not spun up the UI based on
> that assumption.
> Are you looking for feedback that's limited to what can currently be done
> using the API (a CRUD interface for SensorParserConfigs)?
> Thanks,
> Jon
> On Tue, Jan 31, 2017, 7:06 PM Houshang Livian <>
> wrote:
> Hello Metron Community,
> We have constructed a Management Module UI, built on top of METRON-503
> (REST API) (currently under review). This Module gives users the ability to
> setup and administer much of the product through the UI.
> Here are some screens to show you what we are thinking. Please take a look:
> Does this look like a reasonable place to start?
> Is there anything that is an absolute MUST have or MUST NOT have?
> Houshang Livian
> Senior User Experience Designer
> Hortonworks
> ________________________________
> Mobile: (831) 521-4176<tel:(831)%20521-4176>
> ________________________________
> --
> Jon
> Sent from my mobile device

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message