Bug 1086374 - [RFE]sVirt Cluster Policy enforcement
Summary: [RFE]sVirt Cluster Policy enforcement
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Scott Herold
QA Contact: Shai Revivo
URL:
Whiteboard:
: 1086372 (view as bug list)
Depends On: 894084
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-10 17:34 UTC by Arthur Berezin
Modified: 2016-11-29 09:59 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-29 09:59:01 UTC
oVirt Team: Infra
Embargoed:
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
sVirt Cluster Policy Mockup (22.64 KB, image/png)
2014-04-10 17:35 UTC, Arthur Berezin
no flags Details

Description Arthur Berezin 2014-04-10 17:34:12 UTC
Add a cluster policy to allow enforcing sVirt/SELinux on all hosts within a cluster. 

[Mockup Image attached] 

On "add/edit cluster" Window add a tab "Security Policy" which will include configuration options for - sVirt Cluster Policy with options: Enforcing, Permissive, None. 

Clusters' behaviour on each mode:
sVirt Enforcing:
All hosts within the cluster must run with SELinux enabled. 

- When enabling sVirt Enforcing mode, engine to check if all hosts within the cluster have SELinux turned on, if not - enabling sVirt Enforcing policy will fail with appropriate error message. 

- When adding a new host to sVirt Enforcing cluster, if the host does not have SELinux enabled - the host will fail to join the cluster with appropriate error message. 

- When a host changes SELinux Enforcing to SELinux permissive, host will be considered as compromised, an alert should be generated and the host should change status to non-responsive, Admin should be able to configure sVirt policy to migrate running VMs from compromised hosts before changing status to non-operational.


sVirt Permissive: 
Engine continues to monitor hosts' SELinux status, and add alerts instead of talking actions. 

- When enabling sVirt Permissive mode, engine to check which host within the cluster do not have SELinux enabled and generate alert for each host without SELinux enabled. 

- When adding a new host, if host does not have SELinux enabled, an alert will be generated saying the host does not have SELinux enabled and succeed to join the cluster. 

- When a host changes status from Enforcing to Permissive, an alert will be generated. 


None: 
- Hosts' SELinux status will be ignored by engine. 


Hosts' general sub-tab should display SELinux status 


sVirt: 
http://www.redhat.com/rhecm/rest-rhecm/jcr/repository/collaboration/jcr:system/jcr:versionStorage/cddeee980a070d54511c17e2d78baed5/3/jcr:frozenNode/rh:pdfFile.pdf

Comment 1 Arthur Berezin 2014-04-10 17:35:24 UTC
Created attachment 885058 [details]
sVirt Cluster Policy Mockup

Comment 2 Itamar Heim 2014-04-12 19:57:09 UTC
*** Bug 1086372 has been marked as a duplicate of this bug. ***

Comment 5 Moran Goldboim 2016-11-29 09:59:01 UTC
CFME should provide the option for compliance checks.
should be part of RHV and CFME integration.


Note You need to log in before you can comment on or make changes to this bug.