Question on integrating Custom service / Management pack

[Steve Varnau <st...@esgyn.com>]

Hi,

I have worked on defining a custom service and the management pack to plug into Ambari. (In this case for Apache Trafodion project.)

It is working pretty well, but I'm confused on how it can handle upgrading the custom service independently of the HDP stack. A given release of trafodion is compatible with multiple versions of HDP (2.3, 2.4, 2.6), so the mgmt pack is configured to say Traf2.1 works with all three, but then Traf2.2 is also compatible with all three HDP.

In Ambari, trying to register a new version of the stack, I try to change only the URL for trafodion, leaving the URLs for HDP and HDP-UTILS the same, but that is not allowed.  So, I'm confused about how Ambari is expecting custom services to be upgraded.

Thanks for any hints/pointers.

--Steve

RE: Question on integrating Custom service / Management pack

[Steve Varnau <st...@esgyn.com>]

Thanks for confirming I was not missing anything.  Will look forward to v3.

-Steve

> -----Original Message-----
> From: Di Li [mailto:osjiras@gmail.com]
> Sent: Thursday, February 15, 2018 11:00 AM
> To: dev@ambari.apache.org
> Subject: Re: Question on integrating Custom service / Management pack
> 
> Hello Steve,
> 
> From the context of Ambari (express upgrade, rolling upgrade), currently
> you really can't upgrade a custom service (tied to a give HDP stack)
> without upgrading the stack. This is because EU and RU run at the stack
> level, your custom service , from Ambari's point of view, is part of the
> stack.
> 
> Ambari 3.0 (much later this year) will support mpack based EU/RU, where
> you
> can package your service as a stand along stack (single service stack ?)
> that has a dependency on say a given HDP mpack, then you can upgrade your
> mpack without touching HDP.
> 
> But as for Ambari 2.x, if your service is simply a custom service tied to
> an HDP stack, you can't use Ambari RU/EU to *only *upgrade your service.
> 
> 
> 
> On Thu, Feb 15, 2018 at 1:30 PM, Steve Varnau <st...@esgyn.com>
> wrote:
> 
> > Hi,
> >
> > I have worked on defining a custom service and the management pack to
> plug
> > into Ambari. (In this case for Apache Trafodion project.)
> >
> > It is working pretty well, but I'm confused on how it can handle upgrading
> > the custom service independently of the HDP stack. A given release of
> > trafodion is compatible with multiple versions of HDP (2.3, 2.4, 2.6), so
> > the mgmt pack is configured to say Traf2.1 works with all three, but then
> > Traf2.2 is also compatible with all three HDP.
> >
> > In Ambari, trying to register a new version of the stack, I try to change
> > only the URL for trafodion, leaving the URLs for HDP and HDP-UTILS the
> > same, but that is not allowed.  So, I'm confused about how Ambari is
> > expecting custom services to be upgraded.
> >
> > Thanks for any hints/pointers.
> >
> > --Steve
> >
> >

Re: Question on integrating Custom service / Management pack

[Di Li <os...@gmail.com>]

Hello Steve,

From the context of Ambari (express upgrade, rolling upgrade), currently
you really can't upgrade a custom service (tied to a give HDP stack)
without upgrading the stack. This is because EU and RU run at the stack
level, your custom service , from Ambari's point of view, is part of the
stack.

Ambari 3.0 (much later this year) will support mpack based EU/RU, where you
can package your service as a stand along stack (single service stack ?)
that has a dependency on say a given HDP mpack, then you can upgrade your
mpack without touching HDP.

But as for Ambari 2.x, if your service is simply a custom service tied to
an HDP stack, you can't use Ambari RU/EU to *only *upgrade your service.



On Thu, Feb 15, 2018 at 1:30 PM, Steve Varnau <st...@esgyn.com>
wrote:

> Hi,
>
> I have worked on defining a custom service and the management pack to plug
> into Ambari. (In this case for Apache Trafodion project.)
>
> It is working pretty well, but I'm confused on how it can handle upgrading
> the custom service independently of the HDP stack. A given release of
> trafodion is compatible with multiple versions of HDP (2.3, 2.4, 2.6), so
> the mgmt pack is configured to say Traf2.1 works with all three, but then
> Traf2.2 is also compatible with all three HDP.
>
> In Ambari, trying to register a new version of the stack, I try to change
> only the URL for trafodion, leaving the URLs for HDP and HDP-UTILS the
> same, but that is not allowed.  So, I'm confused about how Ambari is
> expecting custom services to be upgraded.
>
> Thanks for any hints/pointers.
>
> --Steve
>
>