WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

[Xen-API] Re: xcp 1.1 rc

To: xen-api@xxxxxxxxxxxxxxxxxxx,xen-api-request@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Re: xcp 1.1 rc
From: "Alexander V. Smirnov" <asmirnov@xxxxxxxxxxxxx>
Date: Fri, 23 Sep 2011 12:58:39 -0400
Delivery-date: Fri, 23 Sep 2011 10:01:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <auto-000001041444@xxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <auto-000001041444@xxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Yesterday I installed an XCP 1.1 RC on two HP blades. When I logged in today with Xen Center I got the 27 days left for the license expiration. I thought it was fixed in the RC.

Alex

On Thu, 22 Sep 2011 23:06:42 -0400
 xen-api-request@xxxxxxxxxxxxxxxxxxx wrote:
Send xen-api mailing list submissions to
        xen-api@xxxxxxxxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.xensource.com/mailman/listinfo/xen-api
or, via email, send a message with subject or body 'help' to
        xen-api-request@xxxxxxxxxxxxxxxxxxx

You can reach the person managing the list at
        xen-api-owner@xxxxxxxxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of xen-api digest..."


Today's Topics:

  1. Re: The method Pool.create_VLAN_from_PIF does not work
     (Jonathan Ludlam)
  2. Re: race condition during /etc/xensource/scripts/vif call
     (Jonathan Ludlam)
  3. Re: Java bindings for XCP-SDK (Jonathan Ludlam)
  4. Re: race condition during /etc/xensource/scripts/vif call
     (George Shuklin)


----------------------------------------------------------------------

Message: 1
Date: Thu, 22 Sep 2011 23:34:44 +0100
From: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] The method Pool.create_VLAN_from_PIF does not
        work
To: ????????? ????????? <wadic@xxxxxxxxxxxxx>
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Message-ID: <43B08DD7-C20A-429F-81E3-A8D24A76AEEA@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="windows-1251"

Looks like you're using the uuids instead of the references? Few API calls take uuids, mostly they use the refs.

Jon

On 21 Sep 2011, at 13:20, ��������� ��������� wrote:

Hi!
I�m using XenAPI .NET library to create external interface on XenServer. Here is my code:

// creating session to hypervisor
hypervisor.Connect();

// creating new network
XenAPI.Network xnet = new XenAPI.Network();
xnet.name_description = this.Domain.Name;
xnet.name_label = "vlan" + vlan.ToString();
XenRef<XenAPI.Network> xnet1 = XenAPI.Network.create(hypervisor.session, xnet);

// get device for new vlan bridging
var eth = PIF.get_all_records(hypervisor.session).Values.Where(v => v.VLAN == -1 && v.device == dev).FirstOrDefault();

// get created network object
var net = XenAPI.Network.get_record(hypervisor.session, xnet1.opaque_ref);

// create vlan interface
List<XenRef<PIF>> pifs = Pool.create_VLAN_from_PIF(hypervisor.session, eth.uuid, net.uuid, (long)vlan);

At this place I have an exception like this:
�Object has been deleted.PIF:a21c28df-d6e8-0980-075d-014bd9cd666e�

I have checked that the objects and eth net have the correct uuid. When I use xe command to create vlan interface with same values �xe pool-vlan-create pif_uuid=� network_uuid=� vlan=�� - its works fine.
What�s wrong?

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx<mailto:xen-api@xxxxxxxxxxxxxxxxxxx>
http://lists.xensource.com/mailman/listinfo/xen-api

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xensource.com/mailman/private/xen-api/attachments/20110922/c24f00e1/attachment.html

------------------------------

Message: 2
Date: Fri, 23 Sep 2011 00:07:03 +0100
From: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] race condition during
        /etc/xensource/scripts/vif call
To: George Shuklin <shuklin@xxxxxxxxxxx>
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Message-ID: <B1B04DE6-FBED-49F4-A048-70D132E058A4@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

Interesting - it might be that you're racing with xapi - it's waiting for the hot plug key to be removed, which is what the xenstore-rm does. Have a look here:

https://github.com/xen-org/xen-api/blob/master/ocaml/xenops/device.ml#L752

(Note that this is more current than XCP 1.0 or 1.1, but the general gist is the same)

Jon

On 22 Sep 2011, at 16:18, George Shuklin wrote:

Good day.
Found strange situation for VM with two or more interfaces: data
from /xapi for domain disappear before vif remove called second time.

Here little patch to vif script (against XCP 1.1 beta) to log XenStore
state:

--- vif.orig    2011-05-19 02:32:19.000000000 +0400
+++ vif 2011-09-22 19:11:10.000000000 +0400
@@ -227,6 +227,8 @@
        xenstore-rm "${HOTPLUG}/hotplug"
    fi
    logger -t scripts-vif "${dev} has been removed"
+    echo ====domid=$DOMID===== >>/var/log/vif-race.log
+    xenstore-ls /xapi >>/var/log/vif-race.log
    remove_from_bridge
    ;;
esac


To see 'strange' add to any vm two interfaces and reboot it.

In vif-race.log for second time vif call:
====domid=3=====
0 = ""
hotplug = ""
 vbd = ""
private = ""
 vbd = ""
  51712 = ""
   ref = "OpaqueRef:1a7992ae-a645-acc6-bf51-3a0202bdd4c7"
frontend = ""
 vbd = ""
3:

(no data for domid 3).

I'm not sure if this is a really serious bug, but I found my
antispoofing patch does not remove rules from OVS for multihomed VM's due lack of 'bridge' variable for VIF (I'm calling remove_restiction()
function in 'remove' case in vif script).

I got this bug in XCP 1.0 and XCP1.1 beta.



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api




------------------------------

Message: 3
Date: Fri, 23 Sep 2011 00:29:54 +0100
From: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] Java bindings for XCP-SDK
To: George Shuklin <george.shuklin@xxxxxxxxx>
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Message-ID: <6331B776-7F29-4FD4-B454-2CC71885D9D0@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

There are some here - they're for XenServer, but should work fine against XCP.

http://community.citrix.com/cdn/xs/sdks/

Jon

On 22 Sep 2011, at 06:55, George Shuklin wrote:

Write your own?

I don't think than XenAPI bindings are very hard to create. XenAPI based on XMLRPC, AFAIK java have plenty things for XML (and XML RPC, may be).

On 22.09.2011 09:40, medhavini buchade wrote:
Hello everyone,

I prefer to code in Java,but the Xen cloud platform SDK provided by Xen does not support Java bindings. So using the SDK libraries is not an option for me. What should i do?

Thank you.


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx<mailto:xen-api@xxxxxxxxxxxxxxxxxxx>
http://lists.xensource.com/mailman/listinfo/xen-api


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx<mailto:xen-api@xxxxxxxxxxxxxxxxxxx>
http://lists.xensource.com/mailman/listinfo/xen-api

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xensource.com/mailman/private/xen-api/attachments/20110923/eb4c39be/attachment.html

------------------------------

Message: 4
Date: Fri, 23 Sep 2011 07:04:27 +0400
From: George Shuklin <george.shuklin@xxxxxxxxx>
Subject: Re: [Xen-API] race condition during
        /etc/xensource/scripts/vif call
To: xen-api@xxxxxxxxxxxxxxxxxxx
Message-ID: <4E7BF73B.4050302@xxxxxxxxx>
Content-Type: text/plain; charset=UTF-8; format=flowed

Ok, may be I was wrong and shall not use any /xapi keys on interface remove. Right now I switched from xapi usage to '$vsctl port-to-br'. But any way, this is kinda strange - why /xapi entery dissapear before interface completely shutdown?

On 23.09.2011 03:07, Jonathan Ludlam wrote:
Interesting - it might be that you're racing with xapi - it's waiting for the hot plug key to be removed, which is what the xenstore-rm does. Have a look here:

https://github.com/xen-org/xen-api/blob/master/ocaml/xenops/device.ml#L752

(Note that this is more current than XCP 1.0 or 1.1, but the general gist is the same)

Jon

On 22 Sep 2011, at 16:18, George Shuklin wrote:

Good day.

Found strange situation for VM with two or more interfaces: data
from /xapi for domain disappear before vif remove called second time.

Here little patch to vif script (against XCP 1.1 beta) to log XenStore
state:

--- vif.orig    2011-05-19 02:32:19.000000000 +0400
+++ vif 2011-09-22 19:11:10.000000000 +0400
@@ -227,6 +227,8 @@
         xenstore-rm "${HOTPLUG}/hotplug"
     fi
     logger -t scripts-vif "${dev} has been removed"
+    echo ====domid=$DOMID=====>>/var/log/vif-race.log
+    xenstore-ls /xapi>>/var/log/vif-race.log
     remove_from_bridge
     ;;
esac


To see 'strange' add to any vm two interfaces and reboot it.

In vif-race.log for second time vif call:
====domid=3=====
0 = ""
hotplug = ""
  vbd = ""
private = ""
  vbd = ""
   51712 = ""
    ref = "OpaqueRef:1a7992ae-a645-acc6-bf51-3a0202bdd4c7"
frontend = ""
  vbd = ""
3:

(no data for domid 3).

I'm not sure if this is a really serious bug, but I found my
antispoofing patch does not remove rules from OVS for multihomed VM's due lack of 'bridge' variable for VIF (I'm calling remove_restiction()
function in 'remove' case in vif script).

I got this bug in XCP 1.0 and XCP1.1 beta.



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api



------------------------------

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api


End of xen-api Digest, Vol 64, Issue 26
***************************************


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>