split config file for HSM service standalone
I have move the 'irs' section from vdsm configure to hsm configure.
There are some problems.
IMHO, only hsm code should directly call 'irs'.
such as vdsm/utils.py
<http://gerrit.ovirt.org/#/c/10363/2/vdsm/utils.py>, should not call hsm
<http://gerrit.ovirt.org/#/c/10363/2/vdsm/libvirtvm.py>, should not call
should hsm service standalone provide a new interface to access the
On 12/04/2012 01:22 AM, Saggi Mizrahi wrote:
HSM is not a package it's an application. Currently it and the rest of VDSM
share the same process but they use RPC to communicate. This is done so that
one day we can actually have them run as different processes.
HSM is not something you import, it's a daemon you communicate with.
----- Original Message -----
From: "Dan Kenigsberg" <dan...@redhat.com>
To: "Saggi Mizrahi" <smizr...@redhat.com>
Cc: "Sheldon" <shao...@linux.vnet.ibm.com>, a...@linux.vnet.ibm.com,
email@example.com, "Zheng Sheng
ZS Zhou" <zhshz...@cn.ibm.com>
Sent: Monday, December 3, 2012 12:01:28 PM
Subject: Re: [vdsm] [VDSM][RFC] hsm service standalone
On Mon, Dec 03, 2012 at 11:35:44AM -0500, Saggi Mizrahi wrote:
There are a bunch of precondition to having HSM pulled out.
On simple things is that someone needs to go through
storage/misc.py and utils.py and move all the code out to logical
There also needs to be a bit of a rearrangement of the code files
so they can import the reusable code properly.
I am also still very much against putting core VDSM in to
Would you elaborate on your position? Do you mind the wrong
this may give about API stability?
IBM Linux Technology Center
vdsm-devel mailing list