- There are cases when the clients need to be reinstalled in big numbers. - There are also cases when the clients need to be removed in bulk. - There are cases when the clients need to be removed because these were the VMs that are not needed any more.
This might be broken into several different tickets
The criteria that can be used for reset or removal can be: - All hosts in a specific group - All hosts of a specific class - All hosts that match a specific filter (naming convention) - All hosts that are not active (we would need to define what that means, for example the ones that you do not respond to ping, or some that are not resolvable any more in the DNS)
It should be possible to combine the criteria: for example remove all hosts in a group A of class B whose names matches C and that are not active any more.
In the case of reset the OTP will be the same for all of the nodes. The reset will clear Kerberos key and cert and set this OTP.
Reset or remove can be the same or different command - TBD.
3.5 but may be deferred till 3.6
The FreeIPA 4.2 was already shaped (see [[milestone:FreeIPA 4.2]] milestone), this does not fit.
I think the request should be simply deferred at all. To me, it does not sound so useful. One can just loop through entries and do actions.
However, if anyone is willing to help and contribute to this one, please let us know!
Metadata Update from @dpal: - Issue assigned to someone - Issue set to the milestone: Tickets Deferred
Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.
Metadata Update from @rcritten: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.