You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Eric Alton (JIRA)" <ji...@apache.org> on 2015/11/02 22:25:27 UTC
[jira] [Updated] (AMBARI-13680) Internal API for custom services to
make configuration updates
[ https://issues.apache.org/jira/browse/AMBARI-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Alton updated AMBARI-13680:
--------------------------------
Description:
A custom (or value-add) service installed after the Ambari stack has been installed may need to change the configuration of an existing service. For example, a change to the hive-env configuration file to add jar files to the HIVE_AUX_JARS_PATH.
I understand the current recommendation for changing another service is through the stackadvisor python script. However, this is only done during the installation of the stack, not afterward.
A custom service added afterward uses the REST APIs to perform the configuration update of an existing service. This requires the user input their Ambari admin username and password when the custom service is being installed. There is concern that users will complain about this requirement.
This feature request is for an internal API which can be used by custom services to request configuration updates through the ambari-server, and which does not require the Ambari admin username or password.
was:
A "value-add" service uses the REST APIs to perform configuration updates through the ambari-server. For example, to add .jar files to a path variable in the hive-env conf file. This requires the user input their Ambari admin username and password when the "value-add" service is being installed. There is some concern that users will complain about this requirement.
This feature request is for an internal API which can be used to request configuration updates through the ambari-server, and which does not require the Ambari admin username or password.
Summary: Internal API for custom services to make configuration updates (was: Internal API for value-add services to make configuration updates)
> Internal API for custom services to make configuration updates
> --------------------------------------------------------------
>
> Key: AMBARI-13680
> URL: https://issues.apache.org/jira/browse/AMBARI-13680
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
> Reporter: Eric Alton
> Labels: features
>
> A custom (or value-add) service installed after the Ambari stack has been installed may need to change the configuration of an existing service. For example, a change to the hive-env configuration file to add jar files to the HIVE_AUX_JARS_PATH.
> I understand the current recommendation for changing another service is through the stackadvisor python script. However, this is only done during the installation of the stack, not afterward.
> A custom service added afterward uses the REST APIs to perform the configuration update of an existing service. This requires the user input their Ambari admin username and password when the custom service is being installed. There is concern that users will complain about this requirement.
> This feature request is for an internal API which can be used by custom services to request configuration updates through the ambari-server, and which does not require the Ambari admin username or password.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)