similar to: Building XCP Debian packages: what sources or repo to use?

Hey guys, Has anyone had much success with XCP and Open Stack together? I''m in the process of putting together a open stack test cluster and I thought I might be able to use XCP dom0''s for it.. but to be honest it doesn''t look so good. I tried following these instructions on a separate XCP test machine: http://wiki.openstack.org/XenServerDevelopment At a first test

Le 06/09/2013 10:14, Thomas Goirand a ?crit : > However, as I wrote it, it's going to happen, so please be patient about > it. IMO, this shouldn't block any transition though. If the release team > is reading: just let everything transition to testing, and remove the > old version of XCP 1.3.2 in testing if that helps, plus add some > blocking bugs so that the rest of Debian

Hi Mike and Jon, If I do this: dpkg -S /usr/lib/python2.7/dist-packages/XenAPI.py then I can see that the XenAPI python package is in fact xcp-xapi. This is quite annoying, because I will need it when building OpenStack nova, but xcp-xapi depends on the Xen hypervisor, which I don't care about when building Openstack. Said in another way: I'd like to avoid having to put

Hello Everyone, I am new with XCP. I''ve setup several hosts with* XCP 1.0* and manage it through XenCenter and command console. Each host has two NICs, one (xenbr0) connected to a physical switch for Internet (said sw1), the other (xenbr3) connected to a physical switch for internal network (said sw2). I am trying to setup VMs and VLANs on xenbr3. I created a virtual bridge by

On 09/24/2013 09:48 PM, St?phane Glondu wrote: > Le 06/09/2013 10:14, Thomas Goirand a ?crit : >> However, as I wrote it, it's going to happen, so please be patient about >> it. IMO, this shouldn't block any transition though. If the release team >> is reading: just let everything transition to testing, and remove the >> old version of XCP 1.3.2 in testing if

Package: xcp-xapi Version: 1.3.2-11 Severity: normal We need to have a separate user/group privilege for xapi and its dependent processes. At the moment, everything runs as root -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux

Package: xcp-xapi Version: 1.3-16 Severity: normal Tags: patch Dear Maintainer, Path to "xe" program in /usr/lib/xcp/bin/xe-mount-iso-sr should be: XE="/usr/bin/xe" HTH, David -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)

Dear all, How to make XCP cannot management by XenCenter? We have an environment about 10 XCP host, and provide about 50 vm for users, We notice that some users want to use XenCenter to connect the XCP host, even they don’t have password, so we want to make XCP cannot use XenCenter and only for console management, is it possible? Sorry for the strange question,

On 09/24/2013 10:04 PM, St?phane Glondu wrote: > Le 24/09/2013 15:48, St?phane Glondu a ?crit : >> If I remove all binary packages of xen-api from testing, the following >> new packages are broken: xcp-guest-templates, nova-xcp-plugins, >> nova-compute-xen. >> >> xcp-guest-templates is built by guest-templates which seems to be a leaf >> package and could be

(CC'ing George Shulkin, and the #680102 bug list) On Sat, Jul 7, 2012 at 4:37 PM, Thomas Goirand <thomas at goirand.fr> wrote: > Hi Mike and Jon, > > It would be really nice if you could have a look at these 3 pending > issues in the Debian bug tracker: > > #675052: xe vm-memory-target-set does not write target to xenstore > #678723: vif-interfaces added to database

Package: xcp-xapi Version: 1.3.2-6 Severity: important Configuration: Two xcp-xapi hosts (default sid/xcp-xapi installation) in single pool. Network backend is bridge. After migration of 'idle' (doning nothing) virtual machine it stops to reply to ping for long time. AFAIK that caused by mac-learning table on upper level (hardware) switch, which route all frames to wrong port

Package: xcp-networkd Version: 1.3.2-13 Severity: serious If apt-get was used to install xcp-networkd instead of dpkg -i, then the debconf value selected for network-type wasn't respected. In other words, the users does: apt-get install xcp-networkd then selects "bridge" in debconf, then it's "openvswitch" which appears in /etc/xcp/network.conf instead of bridge.

Package: xcp-xapi Version: 1.3.2-9 Severity: grave Justification: renders package unusable I've following mostly the xcp-xapi/README.Debian instructions after installing it with apt-get -t wheezy network.conf is configured for bridge, xenbrN are functioning and shown with xe network-list A single SR is present, created with ext on a local LVM. For debugging purposes, all ISO and local ISO

[previously posted to xen-devel@ and xen-api@ but this might be of interest to xen-users@ too] Hi, I''ve refreshed the Xen Cloud Platform (XCP) .isos on xen.org with a new development snapshot (labelled version 0.1.1). XCP is a collaborative effort to build a complete cloud infrastructure platform, complete with a powerful management stack, standards-based APIs, support for multi-tenancy

Package: xcp-xapi Severity: important The README doc mentions: 4/ Configuring Xen and XCP -------------------------- 4.1/ Switch using xl instead of xm and xend to control Xen As of writing, you should do that: sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen Where as the init script checks for: # Exit cleanly if TOOLSTACK != xapi if [ "${TOOLSTACK}" !=

Package: xcp-xapi Version: 1.3-15 Severity: normal By default, xapi listens on the loopback interface. To make it available over the network, its inventory needs to be updated with the bridged interface details. For example, if xenbr0 is the bridged interface, it needs to be set it: lnx200-39:~# cat /etc/xcp/inventory BUILD_NUMBER='0' CURRENT_INTERFACES='xenbr0'

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream If xe pif-configure-ip called twice with different IP, it did not remove old IP from interface (but didn't store both addresses in database). (Checked for management interface) Steps to reproduce: xe pif-reconfigure-ip uuid=... ip=IP1 .... xe pif-reconfigure-ip uuid=(same) ip=IP2 ... 'ip addr show' shows both

Package: xcp-xapi Version: 1.3.2-6 Severity: important I done normal reboot: xe host-disable host=this_host xe host-reboot host=this_host After reboot host stays in 'disable' state and when I've tried to make it enable I got: xe host-enable uuid=ab523ee3-0546-5400-e2db-32f340292fff The specified host is disabled and cannot be re-enabled until after it has rebooted. host:

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream Builin utility for lowlevel vm boot repairment xe-edit-bootloader contains wrong path to xe. IS: XE="/usr/lib/xcp/bin/xe" MUST BE: XE="/usr/bin/xe" -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done