minifi 0.0.1 meetup talk

Apache NiFi – MiNiFiTaking Dataflow Management to the EdgeJoe Percivall - @JPercivall

2 © Hortonworks Inc. 2011 – 2016. All Rights Reserved

About Me• Software Engineer at Hortonworks

• Apache NiFi committer and PMC member

• Github: github.com/JPercivall


Agenda• Why create MiNiFi?

• MiNiFi 0.0.1-Java

• Demo

• Prospective plans




• Demo



• Web-based User Interface for creating, monitoring, & controlling data flows

• Directed graphs of data routing and transformation

• Highly configurable - modify data flow at runtime, dynamically prioritize data

• Easily extensible through development of custom components

• Data Provenance tracks data through entire system

[1] https://nifi.apache.org/

Apache NiFiDataflow


Apache NiFiKey Features

• Guaranteed delivery• Data buffering

- Backpressure- Pressure release

• Prioritized queuing• Flow specific QoS

- Latency vs. throughput- Loss tolerance

• Data provenance• Supports push and pull

models

• Recovery/recording a rolling log of fine-grained history

• Visual command and control

• Flow templates• Pluggable/multi-role

security• Designed for extension• Clustering


Simplified ExampleLet’s consider the needs of a courier service

Physical Store

Gateway Server

Mobile Devices

Registers

Server Cluster

Distribution Center Core Data Center at HQ

Server Cluster

On Delivery Routes

Trucks Deliverers

Delivery Truck: Creative Stall, https://thenounproject.com/creativestall/Deliverer: Rigo Peter, https://thenounproject.com/rigo/Cash Register: Sergey Patutin, https://thenounproject.com/bdesign.by/Hand Scanner: Eric Pearson, https://thenounproject.com/epearson001/

https://thenounproject.com/creativestall/


https://thenounproject.com/rigo/

https://thenounproject.com/bdesign.by/

https://thenounproject.com/epearson001/


Courier service from the perspective of NiFi & MiNiFi

Physical Store

Gateway Server

Mobile Devices

Registers

Server Cluster


Server Cluster

On Delivery Routes

Trucks Deliverers


Client Libraries

Client Libraries

MiNiFi

MiNiFi NiFi NiFi NiFi NiFi NiFi NiFi

Client Libraries











Apache NiFi MiNiFiKey Features





• Data provenance


• Designed for extension

• Design and Deploy• Warm re-deploys


Visual Command and Controlvs.

Design and Deploy


Created to more effectively collect data at the edge




• Demo



NiFi vs MiNiFi Java Processes

NiFi Framework

Components

MiNiFi

NiFi Framework

User Interface

Components

NiFi


NiFi Java Processes

Bootstrap

NiFi

UI

bootstrap.conf

nifi.properties

flow.xml.gzreads &modifies

reads

reads

starts

NiFi MiNiFi


MiNiFi Java Processes

MiNiFi

Bootstrap

ConfigurationChange Notifier(s)

bootstrap.conf

nifi.properties

flow.xml.gzreads

reads

starts

config.ymltransforms

reads

into

NiFi MiNiFi


Same Extensible framework (nars)

In minifi-0.0.1, the nifi-0.6.1 standard processors are bundled (~20mb)– Tailing a Log– UpdateAttribute– Routing by content or attributes– PutEmail

Allows MiNiFi to use NiFi processors


MiNiFi 0.0.1-Java

Declarative configuration of processing flows through a YAML configuration file Exporting of provenance events to another NiFi instance via a Reporting Task over Site to

Site Flow change configuration watcher implementations that provide reloading a NiFi

instance when receiving an updated flow over REST or changes on a file system Providing a mechanism to query an instance's status

<40mb binary distribution

Release Notes


Simple Config.ymlTail a rolling file -> Site to Site


But what about the NiFi.properties values?Can omitted for default values


Provenance Reporting

Site to Site Reporting Task JSON formatted provenance events Configured via config.yml Optional

“SiteToSiteProvenanceReportingTask” in NiFi 0.7.0


A bit more complex Config.ymlTail a rolling File -> Secure Site to Site with Provenance


MiNiFi Toolkit

Convert NiFi templates to config.yml

Validate config.yml files

CLI to facilitate config.yml building


Config Change Notifiers Two implementations

– RestChangeNotifier• Http(s)

– FileChangeNotifier

Configured in bootstrap.conf


Change notifier update

MiNiFi

Bootstrap

ConfigurationChange Notifiers

1. Initial state– Both running



MiNiFi

Bootstrap


user creates new configuration2. User sends update through

notifier– HTTP(S) post request– Change watched file



MiNiFi

Bootstrap


3. Bootstrap validation– Basic validation– Rest notifier will respond

accordingly– Results logged

validate new configuration

user creates new configuration



MiNiFi

Bootstrap


config.ymlsaves new

4. Bootstrap saves and transforms

– Copy old config.yml to a swap file



nifi.properties

flow.xml.gz

transforms into



MiNiFi

Bootstrap


nifi.properties

flow.xml.gz

attempt restart

config.ymlsaves new

reads

transforms into

5. Bootstrap attempts restart– MiNiFi reads in the new

nifi.properties and flow.xml.gz





6. Success or Fail– Successful restart continue

processing– Failure, rollback to old

config– Existing Data is mapped or

orphaned

MiNiFi

Bootstrap


nifi.properties

flow.xml.gz

attempt restart

config.ymlsaves new

reads

transforms into




minifi.sh flowStatus

Components Instance System Diagnostics

Get flow status at the command line




• Demo



Courier service from the perspective of NiFi

Physical Store

Gateway Server

Mobile Devices

Registers

Server Cluster


Server Cluster

On Delivery Routes

Trucks Deliverers


Client Libraries

Client Libraries

MiNiFi

MiNiFi NiFi NiFi NiFi NiFi NiFi NiFi

Client Libraries













• Demo



Prospective Plans MiNiFi 0.0.1-Cpp

– Close to a vote to release– Code itself is 1.2mb without optimization– Data size

• ~20mb for dynamic RAM for heap• Static ~50kb

Configurable Status Reporters– minifi.sh flowStatus -> regular status update

• MQTT?• HTTP?• S2S?

Handle component Annotation Data– UpdateAttribute advanced rules


Major Feature - Centralized Command and Control

Design at a centralized place, deploy on the edge– Flow deployment– NAR deployment– Agent deployment

Version control of flows Agent status monitoring Bi-directional command and control

Centralized management console with a UI


Questions?


Thank you!


Learn more and join us!

Apache NiFi sitehttp://nifi.apache.org

Subproject MiNiFi sitehttp://nifi.apache.org/minifi/

Subscribe to and collaborate [email protected]@nifi.apache.org

Submit Ideas or Issueshttps://issues.apache.org/jira/browse/NIFI

Follow us on Twitter@apachenifi

http://nifi.apache.org/

http://nifi.apache.org/minifi/

http://nifi.apache.org/minifi/

mailto:[email protected]

mailto:[email protected]

https://issues.apache.org/jira/browse/NIFI


Matured at NSA 2006-2014

Brief history of the Apache NiFi Community

• Contributors from Government and several commercial industries

• Releases on a 6-8 week schedule

• Apache NiFi 1.0.0. release on the horizon• Zero-Master Clustering

Code developed at NSA

2006

Today

Achieved TLP

status in just 7 months

July 2015

Code available open source

ASL v2

November 2014


MiNiFi differentiation

Let me get the key parts of NiFi close to where data begins and provide bidrectional communication

NiFi lives in the data center. Give it an enterprise server or a cluster of them. MiNiFi lives close to where data is born and may be a guest on that device or system

minifi 0.0.1 meetup talk

Data & Analytics