On 05/09/2012 05:46 AM, Adam Litke wrote:
On Tue, May 08, 2012 at 11:51:02PM +0300, Dan Kenigsberg wrote:
On Wed, May 09, 2012 at 01:42:45AM +0800, ShaoHe Feng wrote:
$ sudo ./autobuild.sh
build vdsm, and all test OK.
then rpm install the rpm package.
and start the vdsm
$ sudo systemctl
On Mon, 2012-05-07 at 17:07 +0200, Michel van Horssen wrote:
Some extra info:
If I go into virsh on the engine/vdsm and type connect
qemu+tls://192.168.10.79/system I get:
error: unable to connect to server at '192.168.10.79:16514': Connection
refused
(192.168.10.79 is the nodes IP
- Original Message -
This seems interesting.
I am interested in pursuing this further and helping contribute to
the
vdsm lsm integration. lsm is still in the early stages, but i feel
its
the right time to start influencing it so that vdsm integration
can
be
smooth.
I would like to discuss a problem that is going to affect VM creation in the new
REST API. This topic has come up previously and I want to revive that
discussion because it is blocking a proper implementation of VM.create().
Consider a RESTful VM creation sequence:
POST /api/vms/define -
* Mark Wu wu...@linux.vnet.ibm.com [2012-05-09 04:58]:
Hi Guys,
I think people always test their patch before submitting, so
explicitly setting verified is not necessary. More importantly,
verified by the committer is not convincible //enough for code
quality assurance. What's
Hi All,
I am working on moving vdsm.init script to vdsm-tool. But the vdsm.init
script uses some of functions from /etc/init.d/functions. So I plan to
re-code the /etc/init.d/functions or part of it with python code and
also move it to vdsm-tool. Is it okey?
BR.
Wenyi
