[ANNOUNCE] Eugene Chekanskiy as a new Apache Ambari committer

[Yusaku Sako]

Hi all,

It gives me great pleasure to announce that Eugene Chekanskiy has become our 
newest Apache Ambari committer.
Eugene has been involved in the project for over two years making numerous 
contributions to Ambari including but not limited to stack pluggability, 
security issues, etc.

We look forward to your continued involvement to push the project forward.
Congratulations, Eugene!

Yusaku

Re: Why are AMS and LogSearch not part of RU/EU

[Alejandro Fernandez]

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

Re: Why are AMS and LogSearch not part of RU/EU

[Jonathan Hurley]

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

Why are AMS and LogSearch not part of RU/EU

[Di Li]

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