Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 976616

Summary: [Docs] [Admin] [Feature] [Storage] Document that RHEVM now supports RHS hooks
Product: Red Hat Enterprise Virtualization Manager Reporter: Zac Dover <zdover>
Component: DocumentationAssignee: David Ryan <dryan>
Status: CLOSED CURRENTRELEASE QA Contact: Lucy Bopf <lbopf>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.0CC: aburden, asriram, cpelland, gklein, juwu, lbopf, rbalakri, rlandman, sabose, scohen, sdharane, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.5.0Flags: scohen: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: gluster
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 970046 Environment:
Last Closed: 2014-10-22 12:20:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 850483, 970046    
Bug Blocks: 1019470    

Comment 1 Andrew Burden 2013-08-05 08:16:31 UTC 
Hey Sahina,

BZ#970046 is a bit sparse on details but I see it is now ON_QA. Could you please provide any relevant details that might be useful for documentation?

Thank you kindly,
Andrew
Comment 2 Sahina Bose 2013-08-07 05:08:52 UTC 
Hi Andrew,

The feature page http://www.ovirt.org/Features/Gluster_Hooks_Management should give you more details. Please note, that Gluster hooks are different from VDSM hooks - gluster hooks are triggered at gluster volume lifecycle events like create, start, stop.

Please feel free to contact us if you need more details. Also, the RHSC doc team has worked on this content, so you could contact asriram too.
Comment 6 Lucy Bopf 2014-10-22 12:20:21 UTC 
Thanks for checking this, David.

I can verify, then, that the documentation requested in this bug has already been provided.

Since the content has existed since 3.3, I am closing this bug as current release.