Implement something like yum shell
ipa batch << EOF user-add ... user-add ... run EOF
To optimize running many IPA commands at once.
Use case: University: creation of 1000s of user accounts at the beginning of semester.
We should start with at least a quick hack POC and a measurement how much time does "1000x ipa user-add ..." take and how much does "ipa batch" with 1000 user-add's take. This will tell us the priority of the ticket, i.e. how much time it saves.
[mkosek] any chance this can fit in 4.4? We should at least do some quick hack and measure how much time does "1000x ipa user-add ..." takes and how much does "ipa batch" with 1000 user-add's take. pv: first I'd like to see performance of the "new client" atm. The devel version is not performing very well AFAIK. [mkosek] ok, but then I would first like to measure peformance gain of this proposal before moving it to 4.5 to prioritize well in what gets us the most gain adding 1000 hosts using batch command takes 40 seconds vs. 6.5 minutes using separate API calls from Python. I.e. the batch command is 9.75 times faster. pv: that is a considerable improvement. But still it might be better to teach people API batch command with CURL and fix(#5810 (even though I proposed Future releases) then create half-baked solution now. pv: + would be interesting to know why is it 10x faster
This ticket is out of scope of 4.4.0 release. Moving to 4.4.1. Note that 4.4.1 needs to be triaged, therefore not everything will be implemented.
moving out tickets not implemented in 4.4.1
4.4.2 is a stabilization milestone. If this bug is important stabilization bug then please put it to NEEDS TRIAGE milestone for retriage.
Metadata Update from @pvoborni: - Issue assigned to someone - Issue set to the milestone: FreeIPA 4.5 backlog
It is fairly trivial to roll a simple client using the API to do this. I have a blog post outlining how to do this, https://rcritten.wordpress.com/2018/11/02/183/
Metadata Update from @rcritten: - Issue close_status updated to: None
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.