From: Joshua West <jwest@brandeis.edu>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Xen API and PSCSI Devices
Date: Tue, 13 Oct 2009 14:48:53 -0400 [thread overview]
Message-ID: <4AD4CB95.4010505@brandeis.edu> (raw)
Hey folks,
I've noticed that, when using the Xen API, results returned by examining
the list of PSCSI's available to Xen is not updated between calls. It
seems that PSCSI devices are detected once and only once -- upon startup
of xend.
An example of what I'm discussing is:
[root@some-xen-server:~]# python
Python 2.4.3 (#1, Jun 11 2009, 14:09:37)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-44)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import xen.xm.XenAPI as XenAPI
>>> session = XenAPI.Session('http://127.0.0.1:9363')
>>> session.login_with_password('', '')
>>> session.xenapi.PSCSI.get_all()
['45df9686-2da7-52a1-98a0-8a944273d559',
'72bea6df-0fc4-0643-42e8-a5adf07780d7']
...
Attach a new LUN to the host (dom0).
...
>>> session.xenapi.PSCSI.get_all()
['45df9686-2da7-52a1-98a0-8a944273d559',
'72bea6df-0fc4-0643-42e8-a5adf07780d7']
The new LUN is not detected, unless you restart xend. Is this a bug?
Or by design? It would be really nice if the API were to refresh the
list of PSCSI devices detected during each call... or at least have an
API method to instruct xend that it should refresh its listing?
BTW -- I'm doing this on RHEL 5.4 x86_64 with Xen 3.4.1.
Thanks.
--
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu
next reply other threads:[~2009-10-13 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 18:48 Joshua West [this message]
2009-10-14 0:54 ` Xen API and PSCSI Devices Masaki Kanno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD4CB95.4010505@brandeis.edu \
--to=jwest@brandeis.edu \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.