Hi Priyanka

- When you clicked Add Service from the UI, what did you see? Can you share
the ambari log (stdout and stderr) which shows up on the UI when the
component is being installed.

- I see the component is marked as a CLIENT with cardinality 0. Not sure if
you are very rigid about this. If it did not even attempt to install, I
would try to force it to show up on the UI through the Add Service wizard.
Make the component as SLAVE with cardinality 1+. This would force the Add
Service wizard to choose the hosts on which you can install your component.
Example of service which has only slave components:
https://github.com/apache/ambari/tree/trunk/ambari-server/src/main/resources/common-services/PXF/3.0.0

- What behavior do you expect, when a configuration parameter is optional?
It should not show up on UI?

- Posting this in the dev mailing list as well would get you more help.

Regards
Matt

On Thu, Apr 14, 2016 at 2:14 AM, priyanka gugale <[email protected]>
wrote:

> Hi,
>
> I am trying to write a service to install our product package though
> ambari. I have written simple scripts as per guidelines, here is the code
> for same: https://github.com/DT-Priyanka/AmbariDTRTS
>
> I am facing following problems:
> 1. My install scripts are not getting invoked. I tried putting some
> log/print messages to confirm that. When I run install service from UI, it
> exits within a second giving green status.
> (I have not written service_check script, could that be a problem?)
>
> 2. What is the way to mark configurations parameters optional? Whatever
> parameters I include in my config xml file, I need to provide them in UI,
> if I haven't specified defaults. How can I mark them as optional?
>
> Any help on this is really appreciated.
>
> Thanks,
> Priyanka
>
> --
> *Mithun Mathew* (Matt)
>
>    - www.linkedin.com/in/mithunmatt/
>
>
>

Reply via email to