[
https://issues.apache.org/jira/browse/BIGTOP-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14116569#comment-14116569
]
Bruno Mahé commented on BIGTOP-1422:
------------------------------------
This sounds like an interesting idea. But it feels like we are missing another
half of the story.
So I can't wait to read more about it.
But so far, here are my concerns:
* This ticket is about a solution. But I do not see the problem being stated.
So what is the problem this ticket is trying to solve? Why do we need such
solution in the first place?
* I assume debs and rpms will not be replaced by this UPS in the foreseeable
future.
* As I said above, this ticket only talks about one half of the solution. So
provided we have these fancy statically linked tarballs, who or what is going
to manage them? Meaning who or what is going to deploy them, configure them and
ensure services will be started on startup or restarted when updated or
re-configured? With RPM/Debs, it just works after an installation, and I assume
UPS will offer a similar benefit.
* What about the integration with everything else in the world. RPM and Debs
already have every single tool in the world integrating with them, but what
about UPS? How do I manage UPS repositories? How do I update them? What about
conflicts with system package managers?
* Why defining yet another universal packaging? See
http://en.wikipedia.org/wiki/List_of_software_package_management_systems
* 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?
* Why would contributors spend their time on developing a completely new
packaging system when they could work on more interesting things (for example
developing solutions using any of the projects packaged by Apache Bigtop :) ).
We already don't have that much contributors or time to spend on our current
tasks, do you think adding this completely new system is manageable without
straining too much of the contributor's time? Is wandisco going to spend
engineering resources on this?
Oh and also, RPM and debs are far from being outdated :)
> 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.2#6252)
