How plugin SPI should look to support all kinds of communication? Should it be one SPI or several SPIs? Do we allow communication by naming convention (e.g. expect something with given name in extra field)?
===========================
2) EDP plugins - get rid of Oozie hard dependency
We should make EDP pluggable to be able to use not only Oozie in EDP. It's needed to support running Spark / Storm workloads in future using EDP on top of Sahara's provisioned clusters.
===========================
3) Future of EDP
Now we assume that: 1. oozie is used for workflow management 2. all plugins potentially support all job types (may be not implemented)
Do we continue with such assumptions? What other job types need to be added in Juno?
