ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Di Li <osji...@gmail.com>
Subject Re: Why are AMS and LogSearch not part of RU/EU
Date Tue, 21 Feb 2017 14:10:53 GMT
Got it thanks Jonathan and Alejandro.

On Fri, Feb 17, 2017 at 1:47 PM, Alejandro Fernandez <
afernandez@hortonworks.com> wrote:

> Only services that support side-by-side bits can be orchestrated.
> AMS and LogSearch don't have hdp-select to change the symlink of the
> version that is current and can only update the existing bits.
>
> Thanks,
> Alejandro
>
> On 2/17/17, 8:25 AM, "Jonathan Hurley" <jhurley@hortonworks.com> wrote:
>
> >They're not going to be part of those stacks for much longer. As Ambari
> >moves toward management packs in 3.0, they'll be their own stack
> >essentially.
> >
> >To your question - services can provide their own upgrade packs. Since
> >these services are not part of the actual HDP stack, they should not be a
> >part of the HDP pre-defined orchestration. Additionally, they are not
> >"version-able", so Ambari wouldn't know to schedule them. If they provide
> >their own upgrade pack, they can certainly be restarted as part of an HDP
> >orchestration.
> >
> >> On Feb 17, 2017, at 11:21 AM, Di Li <osjiras@gmail.com> wrote:
> >>
> >> Hello fellow Ambari developers,
> >>
> >> I noticed no RU/EU upgrade XML files include AMS or LogSearch. I
> >>understand
> >> they are part of the Ambari repo not the HDP/HDP-UTILS repo, but they
> >>are
> >> still part of the HDP stacks.
> >>
> >> Could any one tell me whether there are any particular reasons that AMS
> >>and
> >> LogSearch are left out of RU/EU, please ?
> >>
> >>
> >> Thank you.
> >>
> >> Di
> >
> >
>
>

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