Bug 1304226

Summary: [RFE] Calamari should emit events for Block device related changes.
Product: Red Hat Ceph Storage Reporter: Darshan <dnarayan>
Component: CalamariAssignee: Christina Meno <gmeno>
Calamari sub component: Back-end QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: ceph-eng-bugs, flucifre, hnallurv, nthomas, vereddy
Version: 1.3.1Flags: gmeno: needinfo? (nthomas)
Target Milestone: rc   
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1334470 (view as bug list) Environment:
Last Closed: 2016-05-09 17:17:02 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:
Bug Depends On:    
Bug Blocks: 1291304, 1334470    

Description Darshan 2016-02-03 05:36:56 UTC 
Description of problem:
calamari should emit events when ever a block device is created / resized or deleted, with all relevant information

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Christina Meno 2016-05-04 15:47:28 UTC 
Nishanth, see concerns here https://github.com/ceph/calamari/pull/436
I suggest that there are two paths forward.

1. I try to add threading to calamari-server and move this polling code up there

2. We migrate this polling eventing/code to be a task that the salt-minion runs 

1 carries more risk to the schedule and 2 is more likely to work without concerns. This is because salt-minion jobs are separate short-live processes. If the rdb ls gets stuck there it is isolated from both calamari and storage console. 

option one carries the risk that it is not a pattern that exists in calamari-server todate and would require me to spend more time there instead of working on https://bugzilla.redhat.com/show_bug.cgi?id=1324671
Comment 4 Christina Meno 2016-05-09 17:17:02 UTC 

*** This bug has been marked as a duplicate of bug 1334470 ***