[
https://issues.apache.org/jira/browse/BIGTOP-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120532#comment-14120532
]
Konstantin Boudnik commented on BIGTOP-1422:
--------------------------------------------
Thanks for chiming in, [~bmahe]. I will try to answer the technical merit
questions in the document I will drop in shortly. Here I want to touch on one
point, namely
bq. If this UPS is only defined and used by Apache Bigtop, why would people
learn a completely new set of tools and process? Why would they care?
Being a market leader in the Hadoop distribution I think this community has
enough leverage to start dictating the industry what and how really Hadoop
should be deploy and managed, right? Seriously, who cares what Linux distro
folks are doing? Hadoop people need rolling upgrades and it seems that only
bundled together balls of tar can deliver the functionality.
bq. Is wandisco going to spend engineering resources on this?
I am not sure why you bringing arbitrary names into the conversation, but say
BIGTOP-297 has a commercial implementation AFAIK, so why not an open-source one
only more universal? Can we have a show of hands from real-life devops people
to see if UPS-like thing would be beneficial for anyone?
> Introduce Universal Packaging System for Hadoop distribution
> ------------------------------------------------------------
>
> Key: BIGTOP-1422
> URL: https://issues.apache.org/jira/browse/BIGTOP-1422
> Project: Bigtop
> Issue Type: New Feature
> Components: build, deployment
> Affects Versions: 0.8.0
> Reporter: Konstantin Boudnik
> Priority: Blocker
> Fix For: 1.0.0
>
>
> Looks like the time comes where Bigtop needs to step up and champion new
> revolutionary format for packaging of the Hadoop.
> New UPS provides completely relocatable archive-like media of distribution
> for the content and the services alike. Preparation of an UPS deliverables
> shouldn't require any special development tools nor particular SDL: only
> cross-platform archives and widely available command-line interpreters would
> be a per-requisite for the creation and installation.
> In our opinion, the separation of the services and content of the
> applications, e.g. .deb and .rpm, are an outdated paradigm, which complicates
> the deployment processes, upgrades, and overall system orchestration.
> Architectural proposal will follow shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
