[jira] [Commented] (FLINK-3090) Create a Parcel Distribution for Cloudera Manager

["Konstantin Boudnik (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212638#comment-15212638 ] 

Konstantin Boudnik commented on FLINK-3090:
-------------------------------------------

As you know, parcels are glorified tarballs with some JSON on top of it to behave like a metadata. The way the parcels are built in practice is as follows: first and RPM package is build using standard Apache Bigtop process. Then the package got unpacked with rpm2cpio and re-packed into tarball+JSON stuff.

What I am saying here, is that having a way to build Linux packages first will give you 90% towards CPTB (aka Cloudera proprietary tar-balls).

> Create a Parcel Distribution for Cloudera Manager
> -------------------------------------------------
>
>                 Key: FLINK-3090
>                 URL: https://issues.apache.org/jira/browse/FLINK-3090
>             Project: Flink
>          Issue Type: Improvement
>          Components: release
>    Affects Versions: 0.10.1
>            Reporter: Johannes
>            Priority: Minor
>
> For ease of deployment it would be nice to provide a parcel distribution of Flink which can be easily managed using Clouder Manager.
> This would set up all necessary dependencies on all machine and starts Flink jobs using yarn.
> A good description of how to get started can be found in the  [Cloudera Manager Extensibility Tools and Documentation | https://github.com/cloudera/cm_ext]
> What needs to be done
> * Create a service description
> * Create a parcel containing the release files
> * Create scripts that can write the appropriate configuration files, taking values from the cloudera manager web config
> For reference [a collection on how this is configured for other services|https://github.com/cloudera/cm_csds], such as Spark.
> Some [starter code | https://github.com/jkirsch/cmflink] can be found here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)