Speaking as a novice, but it seems to me that you can write out the config
value into a system config file (/etc//conf/...) when installing the
service, and then the status function has to read the value from there.
--Steve
> -Original Message-
> From: Dai Xiang
> Sent: Monday, June 25
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
>
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
vice which can participate in an upgrade.
>
> On Jan 20, 2017, at 6:29 PM, Steve Varnau
> mailto:svar...@apache.org>> wrote:
>
>
>
> On 2016-11-21 01:46 (-0800), Janne Valkealahti
> mailto:janne.valkeala...@gmail.com>>
> wrote:
> Ok thanks, is there any j
On 2016-11-21 01:46 (-0800), Janne Valkealahti
wrote:
> Ok thanks, is there any jiras I could follow or generic timeline for these
> enhancements? I understand that if you control a stack you could possible
> pump up versions there but having an addon service you may not have
> anything to upg
y/AMBARI/Service+Advisor
>
> Here's an example of a service_advisor recommending configurations for
> HDFS:
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/service_advisor.py#L131-L149
>
>
> Regards
> Matt
>
Ambari developers,
I'm working on an Ambari MPack to add a service for Trafodion (Apache
incubating). I've figured out the basics, but I'm not sure of the best
technique when my service needs to modify config values for another service. In
this case, we install an HBase co-processor, which is
