[
https://issues.apache.org/jira/browse/AMBARI-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670140#comment-13670140
]
Ximo Guanter commented on AMBARI-2115:
--------------------------------------
The feature provided in the second patch, which isn't part of the first one, is
to have all this process be server-initiated. Ambari Agent registration is
something that the Agent needs to do (with the {{ambari-agent start}} command),
but the bootstrap process in Ambari-Server enables managing this process from
the server, which is very useful.
The server-initiated agent unregistration is basically the inverse of a
bootstrap: the Server will login through SSH to the Ambari-agent machine and
will run {{ambari-agent unregister}} and afterwards it will uninstall
ambari-agent. Since this process is the inverse of a bootstrap, it is
implemented as a DELETE request on the "/bootstrap" URI.
> Support host unregistration
> ---------------------------
>
> Key: AMBARI-2115
> URL: https://issues.apache.org/jira/browse/AMBARI-2115
> Project: Ambari
> Issue Type: New Feature
> Components: agent, build
> Reporter: Ximo Guanter
> Assignee: Ximo Guanter
> Fix For: 1.3.0
>
> Attachments: 0001-Add-support-for-host-unregistration.patch,
> 002-Add-support-for-host-unregistration.patch
>
>
> Right now Ambari is unable to forget a host once it has been registered. This
> makes is tough to use Ambari in a dynamic cluster environment, where clusters
> are torn down and machines are reset to a clean state so they can be reused
> for the next customer.
> If the machine is reset to a clean state without unregistering the host in
> Ambari, the new Ambari client won't be able to register since its cert won't
> match the one Ambari server already has for that host.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
