[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-API] lowlevel access to xapi database
Personally, I think directly accessing the underlying database structures instead of using the API would violate good programming practices. If the API is not able to do what you want it to do, then the API should be improved. -----Original Message----- From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of George Shuklin Sent: Friday, February 18, 2011 11:56 AM To: Jonathan Ludlam Cc: xen-api@xxxxxxxxxxxxxxxxxxx Subject: RE: [Xen-API] lowlevel access to xapi database We running separate database of virtual machines for our purposes and around 1000-1500 VM's syncing starts to be too long and slow. I thought we can use some non-RPC based mechanism to access database (even if this will cost us compability with other versions of xapi). /json actually is RPC too, so it take too much time to use in very 'lively' environment. We need last_boot to know about shutdown reason - it pretty important information. В Пт., 18/02/2011 в 10:17 +0000, Jonathan Ludlam пишет: > Hi George, > > What do you mean by 'fast sync'? Are you using the event.next api? And were you aware of the /json hack that's used for some web gui type things? > > What's the concern with other_config? That's not abnormal XMLRPC encoding as far as I know. I agree that Last_boot_record stands out as being slightly odd, but it's really only intended for internal use. > > Jon > > -----Original Message----- > From: George Shuklin [mailto:george.shuklin@xxxxxxxxx] > Sent: 17 February 2011 23:57 > To: Jonathan Ludlam > Cc: xen-api@xxxxxxxxxxxxxxxxxxx > Subject: Re: [Xen-API] lowlevel access to xapi database > > Thank you. > > We actually wish to have fast sync and XML-RPC seems be to bloated and > have very strange issues with inner objects conversions (f.e. last_boot, > other config and many others strings with format 'parse it yourself'). > > And we feel it can be really interesting to change some values of object > unchangable via XenAPI, for example set every PV VM marked as > 'pv-drivers-up-to-date' (is this field have any meaning for PV guest?), > change their limits without shutdown (they will take place at near > reboot time) and many others. > > On 17.02.2011 12:40, Jonathan Ludlam wrote: > > Not yet, it's internal only. Is there anything you need at the database level that's not available in the API? > > > > Jon > > > > On 10 Feb 2011, at 17:55, George Shuklin wrote: > > > > > >> Good day. > >> > >> I wonder if there is way to access xapi data lower than XenAPI... I > >> means any other way to access them form host where xapi master > >> resides... > >> > >> I look to sources and found some DB interface. It it available outside > >> xapi binary? > >> > >> And I saw some json-related functions. Is any way to get access to data > >> in json format? > >> > >> Thanks. > >> > >> > >> _______________________________________________ > >> 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |