[openstack-dev] [neutron][rootwrap] Performance considerations, sudo?
thierry at openstack.org
Wed Mar 5 15:17:13 UTC 2014
Miguel Angel Ajo wrote:
> The overhead comes from python startup time + rootwrap loading.
> I suppose that rootwrap was designed for lower amount of system calls
Yes, it was not really designed to escalate rights on hundreds of
separate shell commands in a row.
> And, I understand what rootwrap provides, a level of filtering that
> sudo cannot offer. But it raises some question:
> 1) It's actually someone using rootwrap in production?
> 2) What alternatives can we think about to improve this situation.
> 0) already being done: coalescing system calls. But I'm unsure that's
> enough. (if we coalesce 15 calls to 3 on this system we get:
> 192*3*0.3/60 ~=3 minutes overhead on a 10min operation).
> a) Rewriting rules into sudo (to the extent that it's possible), and
> live with that.
We used to use sudo and a sudoers file. The rules were poorly written,
and there is just so much you can check in a sudoers file. But the main
issue was that the sudoers file lived in packaging
(distribution-dependent), and was not maintained in sync with the code.
Rootwrap let us to maintain the rules (filters) in sync with the code
To work around perf issues, you still have the option of running with a
wildcard sudoer file (and root_wrapper = sudo). That's about as safe as
running with a badly-written or badly-maintained sudo rules anyway.
> d) Re-writing rootwrap into C (it's 600 python LOCs now).
(d2) would be to explore running rootwrap under Pypy. Testing that is on
my TODO list, but $OTHERSTUFF got into the way. Feel free to explore
> e) Doing the command filtering at neutron-side, as a library and live
> with sudo with simple filtering. (we kill the python/rootwrap startup
That's as safe as running with a wildcard sudoers file (neutron user can
escalate to root). Which may just be acceptable in /some/ scenarios.
Thierry Carrez (ttx)
More information about the OpenStack-dev