ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mahadev Konar <maha...@hortonworks.com>
Subject Re: Versioned RPMs feature (AMBARI-7257)
Date Fri, 12 Sep 2014 18:07:12 GMT
Nice to see this in BigTop. Adding Raja who's been looking at it. Would be
worth talking this through with respect to BigTop.

thanks
mahadev


On Thu, Sep 11, 2014 at 6:17 PM, Roman Shaposhnik <roman@shaposhnik.org>
wrote:

> Good catch, Alexander!
>
> Btw, looking into this JIRA makes me realized that
> we should probably sync up the design of versioned
> packages between Bigtop and Ambari before
> committing to any particular set of decisions.
>
> Here's the beginning of our discussing on the Bigtop
> side:
>    https://issues.apache.org/jira/browse/BIGTOP-1422
>
> Please let me know how you guys would like to proceed
> so that we can make sure that we have a seamless
> integration.
>
> Thanks,
> Roman.
>
> On Thu, Sep 11, 2014 at 3:58 PM, Alexander Denissov
> <adenissov@pivotal.io> wrote:
> > I noticed a commit today for
> > https://issues.apache.org/jira/browse/AMBARI-7257 which is supposed to
> > enable handling of versioned RPMs.
> >
> > Can anyone shed some light on the requirements, design and implementation
> > for this feature ? It might be useful not only for the HDP stack, and if
> > such, should probably be generalized, especially with the upcoming work
> to
> > support common services across stacks and stack families.
> >
> > --
> > Thanks,
> > Alex.
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message