[
https://issues.apache.org/jira/browse/AMBARI-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873745#comment-13873745
]
Dmitry Lysnichenko commented on AMBARI-4320:
--------------------------------------------
Discussed this question with [~dsen].
Actually, we already have support of issuing CONFIGURE command via api. Exact
call looks like
{code}
curl -X POST 'http://localhost:8080/api/v1/clusters/cc/requests' -u admin:admin
-H "X-Requested-By:anything" --data '{"RequestInfo":{"context":"Zookeeper
server CONFIGURE", "command":"CONFIGURE","service_name":"ZOOKEEPER",
"component_name":"ZOOKEEPER_SERVER", "hosts" : "vm-0.vm"}}'
{code}
Command is actually issued and sent to an agent. There are few minor troubles
(at few service scripts, relevant method is called "config" instead of
"configure"), but everything else seems to work well.
I see two possible ways of issuing this command:
1) issue command directly from the UI during cluster deployment and also when
needed afterwards (prefered).
2) during cluster deployment, issue this command authomatically at
ambari-server during stage creation (like we do with service checks). That
means that we have some internal flag like "unconfigured" for every service
component host. This flag is stored at DB and defaults to "true". If this flag
value is true for some STARTING component during stage creation process,
additional CONFIGURE command is issued. After cluster deployment is finished,
CONFIGURE command is issued manually by UI when configuration is updated. This
way seems to be counter-intuitive.
[~sumitmohanty], are we going to go the 1 way? In this case, I'll open a ticket
for UI and close this jira.
> Add separate CONFIGURE command support to server
> ------------------------------------------------
>
> Key: AMBARI-4320
> URL: https://issues.apache.org/jira/browse/AMBARI-4320
> Project: Ambari
> Issue Type: Improvement
> Components: controller
> Affects Versions: 1.5.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 1.5.0
>
>
> CONFIGURE command is responsible for creating files/dirs, adjusting
> ownership, generating config files etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
