Bug 894460

Summary: Configure ComputeNodes so that libvirt is R/O for all users except for Nova
Product: Red Hat OpenStack Reporter: Perry Myers <pmyers>
Component: openstack-packstackAssignee: Lukas Bezdicka <lbezdick>
Status: CLOSED WONTFIX QA Contact: Ami Jeain <ajeain>
Severity: low Docs Contact:
Priority: medium    
Version: 2.0 (Folsom)CC: aortega, apevec, derekh, jkt, lbezdick, mmagr, oblaut, yeylon
Target Milestone: ---Keywords: CodeChange, FutureFeature, Improvement, Triaged, ZStream
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-18 10:00:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Perry Myers 2013-01-11 20:07:43 UTC
Description of problem:
It could be problematic if admins can run virsh destroy/undefine on ComputeNodes outside of Nova, since that may cause state to get messed up between ComputeNodes and Nova.

So it might be desirable to make libvirt connections read-only for all users except for Nova.

This should be optional though.  Some users may want their admins to have virsh access to VMs even despite the risks.

Comment 2 Daniel Berrangé 2014-09-17 15:14:09 UTC
I think that this is something we should not do.  RHEV made libvirt inaccessible to the root user and it has been a total PITA for anyone logging into a box to troubleshoot the system.

If a person has been given root they are all powerful and know they should be careful. We don't need to add child-locks to their account wrt libvirt, which ultimately don't achieve anything besides annoyance for people who need access.

Comment 3 Daniel Berrangé 2014-09-17 15:17:15 UTC
BTW, Nova copes fine if you 'virsh destroy' a running nova guest - it just transitions it to the shutoff state.