Bug 670700

Summary: Add support to Matahari to replace need for vhostmd SAP agent
Product: [Fedora] Fedora Reporter: Perry Myers <pmyers>
Component: matahariAssignee: Zane Bitter <zbitter>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: ddumas, dpierce, fdanapfe, helge.deller, imain, linux, matahari-maint, nsantos, rdoty, rjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 670003 Environment:
Last Closed: 2012-04-19 19:21:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 668608    
Bug Blocks: 670003    

Description Perry Myers 2011-01-19 02:00:04 UTC
Description of problem:
vhostmd is used presently to provide host level statistics to guests running SAP software.  vhostmd is a custom interface that is only used for SAP running on top of KVM guests.

It would be desirable to move the SAP requirements to a communication transport that is more standardized.  One option is to provide the host level statistics via the Matahari host/guest interface via the virtio-serial transport.

Some notes on what vhostmd does presently:
- vhostmd on the host regularly reads /etc/vhostmd.conf and processes the commands in this XML file to gather the required metrics
- the results form the commands are written into another XML-file which is normally stored in /dev/shm/vhostmd0
- /dev/shm/vhostmd0 hast to be attached as a file-based storage device to any guest that wants to read the metrics
- on the guest "vm-dump-metrics" is called by saposcol to gather the metrics; saposcoll then processes the XML-file and feeds the metrics into the SAP system itself

Comment 1 Richard W.M. Jones 2011-01-19 10:44:47 UTC
Has anyone talked to SAP about this?  They will need to
do extra work on saposocl.

Comment 2 Frank Danapfel 2011-01-19 11:06:29 UTC
Richard, yes there has been a meeting a while ago between Andrew, Perry and the SAP developer who maintains saposcol, and SAP is aware that there might be work required on their side.

Comment 3 Fedora Admin XMLRPC Client 2012-01-11 08:34:47 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Denise Dumas 2012-04-19 19:21:47 UTC
Per Perry, closing this out. Problem will be solved in a different manner.