CIA.vc
"Dube, Lutz" <lutz.dube@ts.fujitsu.com>
Real-time open source activity stats
Stats » Authors » "Dube, Lutz" <lutz.dube@ts.fujitsu.com>
informationsyndicateUTC clock
16:53 on May 25, 2012
event counters
The last message was received 1.78 years ago at 10:00 on Aug 13, 2010
0 messages so far today, 0 messages yesterday
0 messages so far this week, 0 messages last week
0 messages so far this month, 0 messages last month
2 messages since the first one, 1.84 years ago, for an average of 0.92 years between messages
recent messages
dateReversed sort columnprojectcontentlink
12:18 on Aug 11, 2010xen
Commit by "Dube, Lutz" <lutz.dube@ts.fujitsu.com> on default :: 21967:fffedd3d70e1 /tools/python/xen/util/vscsi_util.py:
/rev/fffedd3d70e1
Exception in xen/util/vscsi_util.py while starting xend
?
We have pscsi device with long scsi ids like 15:0:11:101.
In this case lsscsi prints no "blank" between id and type,
so the following split of the string returns wrong output.
The field physical_HCTL is set to 15:0:11:101]dis.
The patch replaces char "]" by "] ", so split() will return the right
physical_HTCL.

Signed-off-by: Lutz Dube Lutz dot Dube at ts dot fujitsu dot com
Acked-by: Ian Jackson <ian dot jackson at eu dot citrix dot com>
--
1: +1/-1
#
16:34 on Jul 23, 2010xen
Commit by "Dube, Lutz" <lutz.dube@ts.fujitsu.com> on default :: 21847:4814e16ea410 /tools/ (4 files in 3 dirs):
/rev/4814e16ea410
tools/xend: Fix performance of xend with more than 10000 FC device paths

On server startup xend start or a later xend restart needs approx. 30 min to
start/restart. Without attached FC devices xend start/restart needs only some
seconds.

server type: Fujitsu Primergy RX600-S5

The time gets lost in xen/xend/XendNode.py line 329 while calling
vscsi_util.get_all_scsi_device().

329 for pscsi_record in vscsi_util.get_all_scsi_devices():
330 scsi_id = pscsi_record['scsi_id']
331 if scsi_id:
332 saved_HBA_uuid = None

I think, in most cases we don't need all the PSCSI devices registered in
xend, but only a few of it.
So a good solution for this perforamce issue is to scan only the SCSI device
paths we need, controlled by a new option in xend-config.sxp.

I have made a patch to allow specification of scsi devices we need in xend
in the config file xend-config.sxp.
The new options pscsi-device-mask expects a list of device ids oder partial
device ids like the option of lsscsi, e.g.
(pscsi-device-mask ('<partial-dev-id1' 'partial-dev-id2' ...))

Without this option set in xend-config.sxp or if lsscsi is not support, all
device paths are process like today.

Signed-off-by: Lutz Dube Lutz dot Dube at ts dot fujitsu dot com
Comment from Masaki Kanno <kanno dot masaki at jp dot fujitsu dot com>: "Well done"
Committed-by: Ian Jackson <ian dot jackson at eu dot citrix dot com>
--
4: +27/-6
#