x/python-ganttclient
Code Issues Proposed changes

First commit of XenAPI-specific code (i.e. connections to the open-source

Browse Source 
community project Xen Cloud Platform, or the open-source commercial product
Citrix XenServer).

A new connection type has been added (xenapi) which means that libvirt calls
will be replaced with calls to XenAPI.

This support depends upon the XenAPI library (available from xen.org).
However, the library is loaded on-demand, so there is no need for the library
to be present unless you actually want to use XenAPI.  The same is true of
libvirt, so there is no need to have libvirt present if you are only using
XenAPI.

This work is incomplete.  The VMs don't actually start yet, and won't
until we settle on the proposed refactoring for bootable volumes.  Also,
VM console support is not yet refactored.

Finally, xenapi.py does not support the metrics monitoring calls used by
monitor.py (block_stats, interface_stats).  XenAPI already includes HTTP
access to RRDs for retrieving aggregated stats, so there is no need for
monitor.py at all (xapi does it for you).  The plan is to arrange for those
RRDs to be passed straight to the reporting layer without the need for
the aggregation code in nova-monitorinstance.
This commit is contained in:
Ewan Mellor
2010-07-18 18:28:21 +01:00
parent c2ffc9150e
commit 1a723ab89f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
nova/flags.py
View File

@@ -36,7 +36,7 @@ DEFINE_bool = DEFINE_bool
# Define any app-specific flags in their own files, docs at:
# http://code.google.com/p/python-gflags/source/browse/trunk/gflags.py#39
DEFINE_string('connection_type', 'libvirt', 'libvirt or fake')
DEFINE_string('connection_type', 'libvirt', 'libvirt, xenapi or fake')
DEFINE_integer('s3_port', 3333, 's3 port')
DEFINE_integer('s3_internal_port', 3334, 's3 port')
DEFINE_string('s3_host', '127.0.0.1', 's3 host')