kanidm: Orca setup script is broken

Well, mostly I was thinking about the way I approached orca in the past was “benchmark” and I modelled a lot of things on ldclt from 389-ds which is their benchmark tool.

But recently @jinnatar pointed out she wanted to see an “enterprise simulator”. Where the benchmark isn’t just “sterile” kind of do-searches like ldclt was doing, but should be about simulating user actions.

Then that got me thinking about a way to potentially use that as a basis to not only do an enterprise simulator, but also how to potentially model a more controlled test mode.

Currently the design has workers that take a task queue and then execute the tasks and report on the stats. That ends up with a thread-per-worker and each worker just shoves out tasks etc. But it’s hard to see how the tasks the correspond to a user, or different things, and it’s hard to do other kinds of interactions.

Instead, I think we could do it like erlang. Instead of workers, we spawn a task for each “person”. Then each of these tasks has a little schedule, like “login, click about, idle for some time, then do some more etc”. It models how a person would interact. At the start of the test, we can have each “task” create it’s own user/password etc, rather than the crazy batch thing we have now. It also allows easier interleaving of things naturally based on user interactions.

We still need a centralised stats-collector but that model already exists, so we can time operations for each task.

This also then makes it easier to do different kinds of tests later like the high-search load tests (direct each “person” to just search) etc.

I think for now we drop the LDAP support too, we can add that back later,

Did some poking around this and from what I can infer, dropping the add to idm_admins & just switching orca to use idm_admin instead of admin should be the right way to go. At least it now succeeds conntest and from what I can read from the sources, all actions performed are in the domain of idm_admins and not system_admins.

So the problems in order are:

1. The setup script should infer the password for idm_admin
2. Orca needs to be patched for using idm_admin instead of admin and to no longer attempt adding admin into idm_admins.
3. Orca has plenty of other compatibility issues as well, but those should be new separate issues. I’d say when conntest passes, this one is done.