[ 
https://issues.apache.org/jira/browse/AMBARI-8815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hari Sekhon updated AMBARI-8815:
--------------------------------
    Description: 
Instead of installing lots of RPMs consider adding Parcel support as is done in 
Cloudera Manager.

I wasn't sure about it when we first started using it in Cloudera but it's 
actually much simpler and cleaner.

A Parcel is basically just a tarball that you unpack to /opt/<stack>/<version> 
and then link /opt/<stack>/current to the currently active version so you can 
easily keep lots of them adjacently.

It also simplifies deploying a stack since there is no variation of what is 
installed and what is missing, it's always the same directory tree and linking 
is very simple (much simpler than the latest HDP 2.2 attempt where 
/usr/hdp/current doesn't actually map straight to the version dir meaning you 
can't just use /usr/hdp/current/... as the prefix for all commands like you 
should be able to - as I used to do on Cloudera).

Having a static prefix that is relinked like /opt/<stack>/current would make 
commands portable across different versions of the stack, a major win compared 
to the current HDP 2.2 implementation where you need to explicitly specify a 
prefix containing the exact version eg. /usr/hdp/2.2.0.0-2041/ - which is not 
portable at all (this might actually just be because the symlinks under 
current/ are named differently to what they link to though).

Regards,

Hari Sekhon
(ex-Cloudera)
http://www.linkedin.com/in/harisekhon

  was:
Instead of installing lots of RPMs consider adding Parcel support as is done in 
Cloudera Manager.

I wasn't sure about it when we first started using it in Cloudera but it's 
actually much simpler and cleaner.

A Parcel is basically just a tarball that you unpack to /opt/<stack>/<version> 
and then link /opt/<stack>/current to the currently active version so you can 
easily keep lots of them adjacently.

It also simplifies deploying a stack since there is no variation of what is 
installed and what is missing, it's always the same directory tree and linking 
is very simple (much simpler than the latest HDP 2.2 attempt where 
/usr/hdp/current doesn't actually map straight to the version dir meaning you 
can't just use /usr/hdp/current/... as the prefix for all commands like you 
should be able to - as I used to do on Cloudera).

Having a static prefix that is relinked like /opt/<stack>/current would make 
commands portable across different versions of the stack, a major win compared 
to the current HDP 2.2 implementation where you need to explicitly specify a 
prefix containing the exact version eg. /usr/hdp/2.2.0.0-2041/ - which not 
portable at all (this might actually just be because the symlinks under 
current/ are named differently to what they link to though).

Regards,

Hari Sekhon
(ex-Cloudera)
http://www.linkedin.com/in/harisekhon


> Add Parcel support similar to Cloudera Manager
> ----------------------------------------------
>
>                 Key: AMBARI-8815
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8815
>             Project: Ambari
>          Issue Type: Improvement
>          Components: stacks
>    Affects Versions: 1.7.0
>         Environment: HDP 2.2
>            Reporter: Hari Sekhon
>
> Instead of installing lots of RPMs consider adding Parcel support as is done 
> in Cloudera Manager.
> I wasn't sure about it when we first started using it in Cloudera but it's 
> actually much simpler and cleaner.
> A Parcel is basically just a tarball that you unpack to 
> /opt/<stack>/<version> and then link /opt/<stack>/current to the currently 
> active version so you can easily keep lots of them adjacently.
> It also simplifies deploying a stack since there is no variation of what is 
> installed and what is missing, it's always the same directory tree and 
> linking is very simple (much simpler than the latest HDP 2.2 attempt where 
> /usr/hdp/current doesn't actually map straight to the version dir meaning you 
> can't just use /usr/hdp/current/... as the prefix for all commands like you 
> should be able to - as I used to do on Cloudera).
> Having a static prefix that is relinked like /opt/<stack>/current would make 
> commands portable across different versions of the stack, a major win 
> compared to the current HDP 2.2 implementation where you need to explicitly 
> specify a prefix containing the exact version eg. /usr/hdp/2.2.0.0-2041/ - 
> which is not portable at all (this might actually just be because the 
> symlinks under current/ are named differently to what they link to though).
> Regards,
> Hari Sekhon
> (ex-Cloudera)
> http://www.linkedin.com/in/harisekhon



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

Reply via email to