All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Eric Camachat <eric.camachat@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: xend with XenAPI in stackless python-2.7
Date: Fri, 1 Nov 2013 17:34:23 +0000	[thread overview]
Message-ID: <5273E61F.5080701@citrix.com> (raw)
In-Reply-To: <CACeEFf4oTu9mdm3dy_rdsF9iPkOGexbQ-Mj6FusTpw46ndOpQw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3644 bytes --]

On 01/11/13 17:05, Eric Camachat wrote:
> Hi,
>
> I am using XEN-4.1.2 and linux-2.6.32 as dom0.
> After I upgraded stackless python from 2.5 to 2.7 (and rebuilt xen).
> XenAPI became unusable, I spent some time to investigate XenAPI,py, it
> looks fine.
> So, I guess xend has problem with python 2.7, because it always
> returned method unknown.
> Do I have to tweak xend to let it support python 2.7?
>
> Thanks,
> Eric

xend and XenAPI are two completely different things.

xend is the old deprecated Xen toolstack, written entirely in python. 
It has been replaced with the xenlight toolstack upstream.

Xen-API is a separate open source toolstack, written in OCaml. 
XenAPI.py is just a small python wrapper around the Xen-API XMLRPC
interface.

Which toolstack are you expecting to be using?

~Andrew

>
> /root #
> python                                                                                                      
>
> Python 2.7.5 Stackless 3.1b3 060516 (default, Oct 31 2013,
> 16:45:11)                                                
> [GCC 4.2.2] on
> linux2                                                                                               
>
> Type "help", "copyright", "credits" or "license" for more
> information.                                              
> >>> import
> XenAPI                                                                                                   
>
> >>> session =
> XenAPI.xapi_local()                                                                                   
>
> >>> session.login_with_password('',
> '')                                                                             
>
> Traceback (most recent call
> last):                                                                                  
>
>   File "<stdin>", line 1, in
> <module>                                                                               
>
>   File "/usr/lib/python2.7/site-packages/XenAPI.py", line 198, in
> <lambda>                                          
>     return lambda *params: self._login(name,
> params)                                                                
>   File "/usr/lib/python2.7/site-packages/XenAPI.py", line 171, in
> _login                                            
>     self.API_version =
> self._get_api_version()                                                                      
>
>   File "/usr/lib/python2.7/site-packages/XenAPI.py", line 186, in
> _get_api_version                                  
>     pool =
> self.xenapi.pool.get_all()[0]                                                                            
>
>   File "/usr/lib/python2.7/site-packages/XenAPI.py", line 245, in
> __call__                                          
>     return self.__send(self.__name,
> args)                                                                           
>
>   File "/usr/lib/python2.7/site-packages/XenAPI.py", line 149, in
> xenapi_request                                    
>     result = _parse_result(getattr(self,
> methodname)(*full_params))                                                 
>
>   File "/usr/lib/python2.7/site-packages/XenAPI.py", line 219, in
> _parse_result                                     
>     raise
> Failure(result['ErrorDescription'])                                                                       
>
> XenAPI.Failure: ['MESSAGE_METHOD_UNKNOWN',
> 'pool.get_all']                                                          
> >>>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


[-- Attachment #1.2: Type: text/html, Size: 13539 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-11-01 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 17:05 xend with XenAPI in stackless python-2.7 Eric Camachat
2013-11-01 17:34 ` Andrew Cooper [this message]
2013-11-01 18:12   ` Pasi Kärkkäinen
2013-11-04 10:30     ` Ian Campbell
2013-11-01 18:14   ` Eric Camachat
2013-11-04 10:32     ` Ian Campbell

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=5273E61F.5080701@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=eric.camachat@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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.