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

Peter Linnell commented on BIGTOP-1422:
---------------------------------------

While I will wait for Cos' proposal, I will say the Cloudera parcel,  as is, 
does have some draw backs.  

I can understand the wish for a rolling upgrade, the upgrade time can be made 
shorter certainly for rpm with tools like spacewalk. SUSE even wrote a 
whitepaper for deploying and upgrading Hadoop distros using spacewalk. If the 
update or downgrade does not work, its a bug in Bigtop or any other distro. 
Also spacewalk is massively scalable. It can manage very large clusters +4k 
easily.

As Cos mention shuffling around 1Gb tarballs is suboptimal for a minor update. 

As some users do not let Hadoop admins touch the system packages, likewise 
there are other companies I know which would be quite allergic to not having 
things in rpm format, as their in-house tools can do a lot with rpm, like 
signature verification and auditing among others. 

As BMahe mentions, rpms and debs are far from obsolete. 

Just my 0.02

> 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)

Reply via email to