Re: [Openstack-operators] [openstack-dev] [nova][xenapi] can we deprecate the xenapi-specific 'nova-console' service?

Hi Melanie, We recommend using novncproxy_base_url with vncserver_proxyclient_address set to the dom0's management IP address. We don't currently use nova-console, so deprecation would be the best approach. Thanks, Bob -Original Message- From: melanie witt [mailto:melwi...@gmail.com]

Re: [openstack-dev] [nova][xenapi] can we deprecate the xenapi-specific 'nova-console' service?

Hi Melanie, We recommend using novncproxy_base_url with vncserver_proxyclient_address set to the dom0's management IP address. We don't currently use nova-console, so deprecation would be the best approach. Thanks, Bob -Original Message- From: melanie witt [mailto:melwi...@gmail.com]

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

> Yeah, the nova.CONF cpu_allocation_ratio is being overridden to 0.0: The default there is 0.0[1] - and the passing tempest-full from Zuul on https://review.openstack.org/#/c/590041/ has the same line when reading the config[2]: We'll have a dig to see if we can figure out why it's not

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

We're not running with [1], however that did also fail the CI in the same way - see [2] for the full logs. The first failing appeared to be around Aug 27 08:32:14: Aug 27 08:32:14.502788 dsvm-devstack-citrix-lon-nodepool-1379254 devstack@placement-api.service[13219]: DEBUG

Re: [openstack-dev] [nova] reboot a rescued instance?

Hi Matt, My understanding is that this is being used by Rackspace. AFAIK the change isn't upstream because there was no sensible way to permit reboot of a rescued instance for XenAPI users but prevent it for other drivers. I'd be hesitant to permit reboot-from-rescue for all drivers as I'm not

Re: [openstack-dev] [nova][xenapi] does get_all_bw_counters driver call nova-network only?

As far as I remember this isn't a nova-network only feature; but I may be missing something. I believe the bandwidth counters may be being used at Rackspace. Bob -Original Message- From: Balázs Gibizer [mailto:balazs.gibi...@ericsson.com] Sent: 16 April 2018 13:37 To: OpenStack-dev

Re: [openstack-dev] Debian OpenStack packages switching to Py3 for Queens

Sent: Thursday, 15 February 2018 6:39 p.m. To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] Debian OpenStack packages switching to Py3 for Queens 2018-02-15 11:25 GMT+01:00 Bob Ball <bob.b...@c

Re: [openstack-dev] Debian OpenStack packages switching to Py3 for Queens

Hi Thomas, As noted on the patch, XenServer only has python 2 (and some versions of XenServer even has Python 2.4) in domain0. This is code that will not run in Debian (only in XenServer's dom0) and therefore can be ignored or removed from the Debian package. It's not practical to convert

Re: [Openstack] [xenserver][ocata] overcommit vcpu

Hi Adhi, Do you mean that you can’t run two VMs each with 8 vCPUs, or do you mean that you are trying to run one VM with more than 8 vCPUs? I believe that the cpu_allocation_ratio means that you can re-use each physical cpu (thread) up to 16 times with different VMs, but each VM is still

Re: [openstack-dev] vGPUs support for Nova - Implementation

Hi Sahid, > > a second device emulator along-side QEMU. There is no mdev > > integration. I'm concerned about how much mdev-specific functionality > > would have to be faked up in the XenServer-specific driver for vGPU to > > be used in this way. > > What you are refering with your DEMU it's

Re: [openstack-dev] vGPUs support for Nova - Implementation

Hi Sahid, > Please consider the support of MDEV for the /pci framework which provides > support for vGPUs [0]. From my understanding, this MDEV implementation for vGPU would be entirely specific to libvirt, is that correct? XenServer's implementation for vGPU is based on a pooled device model

Re: [Openstack] [xenserver-ocata] neutron-dhcp/metadata agent on XenServer

Hi Adhi, If the Neutron agents would normally run with the nova compute services, then they would need to run in the compute VM when deploying with XenServer, not in domain 0. I would assume that the DHCP agents should also run in the compute VM. Also added

Re: [Openstack] [Ocata-Xenserver] Nova-compute wouldn't start

Hi Adhi, Please see bug report at https://bugs.launchpad.net/nova/+bug/1693147 which I believe covers your issue. Huan is working on a fix at https://review.openstack.org/#/c/467926 Thanks, Bob From: Adhi Priharmanto [mailto:adhi@gmail.com] Sent: 18 May 2017 17:52 To: Bob Ball <bo

Re: [Openstack] [Ocata-Xenserver] Nova-compute wouldn't start

the compute will not start. Bob From: Adhi Priharmanto [mailto:adhi@gmail.com] Sent: 18 May 2017 16:40 To: Bob Ball <bob.b...@citrix.com> Cc: openstack <openstack@lists.openstack.org>; #OpenStack External Email <openst...@citrix.com> Subject: Re: [Openstack] [Ocata-Xenserver] Nov

Re: [Openstack] [Ocata-Xenserver] Nova-compute wouldn't start

Hi Adhi, Very interesting. I suspect that self._get_vif_ref, below, is returning None. This appears to be when the VM does not exist on the host - perhaps the VM was renamed, deleted, or it has been migrated to a different host and Nova’s records didn’t get updated? I believe the issue is

Re: [OpenStack-Infra] Initial member for os-xenapi-release

On 2016-11-24 02:44, Bob Ball wrote: > Please could the initial member or owner for os-xenapi-release be set to > os-xenapi-core so we can modify the members of the group. > > Link to group: > https://review.openstack.org/#/admin/groups/1650,members > Review that cr

[OpenStack-Infra] Initial member for os-xenapi-release

Hi, Please could the initial member or owner for os-xenapi-release be set to os-xenapi-core so we can modify the members of the group. Link to group: https://review.openstack.org/#/admin/groups/1650,members Review that created group: https://review.openstack.org/#/c/400153/ Thanks, Bob

Re: [openstack-dev] [neutron] proposal to resolve a rootwrap problem for XenServer

>> Side note: we should first have Xen third-party CI testing running > > It already is running > Oh right. It does not validate the new change though. Would be nice to see > the new ‘daemon’-ic mode behaves in real world. 100% agreed. I'll work with Jianghua to make sure we get automated

Re: [openstack-dev] [neutron] proposal to resolve a rootwrap problem for XenServer

Hi Ihar, > I am puzzled. Is Neutron the only component that need to call to dom0? No it's not. Nova has similar code to call plugins in dom0[1], and Ceilometer will also need to make the calls for some metrics not exposed through the formal API. We don't want code duplication, and are

Re: [openstack-dev] [neutron] proposal to resolve a rootwrap problem for XenServer

> > Oslo.privsep seem try to launch a daemon process and set caps for this > daemon; but for XenAPI, there is no need to spawn the daemon. > > I guess I'm lacking some context... If you don't need special rights, why use > a > rootwrap-like thing at all ? Why go through a separate process to

[OpenStack-Infra] Please change owner of os-xenapi-{core/ci}

The os-xenapi-core[1] and os-xenapi-ci[2] gerrit groups were created as a result of my review at https://review.openstack.org/386528 Please could the owner of os-xenapi-core be set to me (bob-ball) and the owner of os-xenapi-ci be set to os-xenapi-core. Many thanks, Bob [1] https

Re: [Openstack] Security Groups Can't Apply in Kilo with Neutron & XenServer

Hi Adhi, Ccould you provide more details about how you’re installing Liberty, including your local.conf (if using devstack) and the nova / neutron configuration files? Also details about how you’re booting the instance and what security groups you’re expecting to be applied. Thanks, Bob

Re: [openstack-dev] Nova mascot

> TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll be > missed. :-) It also seems from http://www.openstack.org/project-mascots that the majority of OpenStack projects have selected a mascot. I think it would be a great shame if the Nova project didn’t have an easily

[OpenStack-Infra] Please change owner of fuel-plugin-xenserver-ci

The fuel-plugin-xenserver-ci gerrit group (https://review.openstack.org/#/admin/groups/1450,info) was created as a result of https://review.openstack.org/#/c/334558/ - please could the owner of the group be updated to be fuel-plugin-xenserver-core so we can modify the members of the

[openstack-dev] [fuel] [plugins] Requesting voting permissions

The ACL at https://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/fuel-plugin-xenserver.config shows that, in order for our CI to vote on the fuel-plugins-xenserver project, we need to be in the fuel-plugins-ci group. As such, could I request that the "Citrix

Re: [openstack-dev] [tempest] Discussion on to enable "Citrix XenServer CI" to vote openstack/tempest

Hi Masayuki, We have been running against Tempest and commenting for many months (years?) and run in the Rackspace public cloud so have no capacity issues. Indeed the execution time is longer than other jobs, because we actually have to use double nesting (Devstack running on Ubuntu in a VM

[openstack-dev] [Nova] Virtual GPU provisioning

How should we expose Virtual GPUs to Nova? Various discussions have happened on the original spec submission for Mitaka[1] and the recent submission for Newton[2], however there are a few questions which need further discussion. But before those question (at the end), some thinking behind the

Re: [Openstack] [OpenStack-Infra] [third-party][openstack][CI] Examples required for "single_node_ci_data.yaml" config file

You need your own credentials where I put - I just didn’t want to share my credentials with the whole OpenStack community ☺ Bob From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com] Sent: 10 May 2016 10:04 To: Bob Ball <bob.b...@citrix.com> Cc: openstack-in...@lists.opensta

Re: [OpenStack-Infra] [third-party][openstack][CI] Examples required for "single_node_ci_data.yaml" config file

You need your own credentials where I put - I just didn’t want to share my credentials with the whole OpenStack community ☺ Bob From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com] Sent: 10 May 2016 10:04 To: Bob Ball <bob.b...@citrix.com> Cc: openstack-infra@lists.openstack.org;

Re: [Openstack] [OpenStack-Infra] [third-party][openstack][CI] Examples required for "single_node_ci_data.yaml" config file

Hi Abishek, I use the following which works well: oscc_file_contents: | # Do Not Edit - Generated & Managed by Puppet clouds: rax: profile: rackspace regions:

Re: [openstack-dev] [nova] FYI: Citrix XenServer CI is disabled from voting

The failure rate was indeed 100%; there were some requirements on packages not installed in our CI environment (libssl-dev libffi-dev) which were causing all failures. This is now fixed and the CI is back to voting on passing changes. I have re-queued all jobs which failed in less than 6

Re: [openstack-dev] [nova] driver review dashboards

Hi Sean, > [section "XenServer"] > query = label:Code-Review>=1,bob.b...@citrix.com file:xenserver I believe this should be file:xenapi? Can you match multiple files here? Most files are under the xenapi trees, but it would miss some files in plugins/xenserver and not in

Re: [Openstack] [Fuel] How to configure Xen + Libvirt using Fuel 8.0

Subject: Re: [Openstack] [Fuel] How to configure Xen + Libvirt using Fuel 8.0 From: Martinx - ジェームズ To: Bob Ball CC: Mike Scherbakov ,Ashish Yadav ,Fabrizio Soppelsa ,openstack@lists.openstack.org >From time to time, randomly, XenServer loses all virtual machine definitions, >and

Re: [Openstack] [Fuel] How to configure Xen + Libvirt using Fuel 8.0

XenServer is fully open source - XCP is no longer. You can download XenServer for free from www.XenServer.org without any contact with Citrix. For libvirt+Xen AFAIK that plugin doesn't exist and you would need to manually configure each compute node after installation. The XenServer plugin

Re: [OpenStack-Infra] [Third-party-announce] Four Cisco CI systems are disabled

I had a consistent issue with zuul-merger failing to merge due to incorrect host keys set up by the community puppet modules. See https://review.openstack.org/#/c/266041/ for the fix, but note that we must have a newline at the end of the gerrit_ssh_host_key. You can easily confirm if you are

Re: [OpenStack-Infra] XenServer & RDO

This is indeed the wrong list to ask on, however check out https://www.citrix.com/blogs/2015/11/30/integrating-xenserver-rdo-and-neutron/ for a step-by-step guide for installing XenServer + RDO Thanks, Bob From: cac...@quantum-sci.com [mailto:cac...@quantum-sci.com] Sent: 27 January 2016

Re: [openstack-dev] [Nova][Glance] Xenplugin + Glance_v2 = Hate

Hi Mikhail, Unfortunately I completely agree that using Glance with the XenServer plugin is painful. As Keven pointed out, the current release of XenServer includes python 2.4 in dom0 (where the plugin runs) so having a dependency on nova.image or glanceclient is likely to introduce more pain

Re: [openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave Libvirt on Wizard

> On Mon, Dec 21, 2015 at 1:43 PM, Igor Kalnitsky > wrote: > > What about hypervisor "Qemu", and checkbox option on Settings tab - > > "Use KVM extension"? > Qemu is not a hypervisor This will be even more confusing. > I think "Libvirt" + some tooltip which says "Qemu and

Re: [OpenStack-Infra] Thirdparty CI: XenProject CI Failures result in 404 (no logs)

Sorry – just got to this mail. Just to be clear, this was a transient failure on the 7th December, which is now fixed. The most recent recheck was successful and http://zuul.openstack.xenproject.org/scoreboard/?project=openstack%2Fnova=jenkins%2CXenProject-CI=48==_size=100 shows the

Re: [openstack-dev] [devstack]Question about using Devstack

Hi, Devstack is intended for development, so when you reboot it is not expecting to be able to preserve any information, and will give you a fresh environment to continue development on. The XenServer devstack installation uses a separate VM, but devstack is automatically run at boot, as

Re: [openstack-dev] [devstack]Question about using Devstack

Ah yes - I’d forgotten about OFFLINE=True (shows how often I use it!) If you set this in your localrc file then yes, in theory it should work offline – but will still generate a new environment when you reboot the VM. Bob From: yatin kumbhare [mailto:yatinkumbh...@gmail.com] Sent: 23 November

Re: [openstack-dev] [devstack]Question about using Devstack

mode, but you may be able to use other services if you remove tempest from ENABLED_SERVICES. @jordan.pittier @Bob Ball If I can ensure my IP address , localrc and everything else are not changed, is there any way I can achieve my goal? I don’t think I understand what your goal is – perhaps

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

There was a conversation a while ago around explicitly avoiding the empty namespace - see http://lists.openstack.org/pipermail/openstack-dev/2014-July/041238.html The approach I have used since is "xenserver: recheck" and "xen: recheck". I think the appropriate command should be "fuel:

Re: [openstack-dev] [Openstack-operators] [nova] can we deprecate the xvp console?

> I noticed today that nova.console.xvp hits the database directly for > console pools. We should convert this to objects so that the console > service does not have direct access to the database (this is the only > console I see that hits the database directly). However, rather than go > through

Re: [Openstack-operators] [nova] can we deprecate the xvp console?

> I noticed today that nova.console.xvp hits the database directly for > console pools. We should convert this to objects so that the console > service does not have direct access to the database (this is the only > console I see that hits the database directly). However, rather than go > through

Re: [Openstack] [Fuel] v7.0 error during deployment

I’ve consistently had the same problem. A quick fix for me was to change the NTP servers to “10.20.0.1” (or whatever the local IP address of your Fuel master is), then you only have to worry about the NTP settings for the fuel master. Bob From: Adam Lawson [mailto:alaw...@aqorn.com] Sent: 22

Re: [openstack-dev] [all][third-party][ci] Announcing CI Watch - Third-party CI monitoring tool

-Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: 25 August 2015 01:44 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all][third-party][ci] Announcing CI Watch - Third-party CI monitoring tool We have a number of people working on

Re: [Openstack] XenServer 6.5 or KVM

Hi Leandro, It is true that the majority of development work, and the majority of deployments, happen with the libvirt+KVM combination however there are some major deployments that use XenServer highly effectively. Regarding Neutron support, yes there are a number of known areas where we need

Re: [Openstack] XenServer 6.5 or KVM

. If you want to use XenServer then community member Bob Ball (bob.b...@citrix.commailto:bob.b...@citrix.com) can help you more with this. Best regards, Martins On 2015.07.24. 05:03, Leandro Mendes wrote: Hi Guys, I'm trying to setup a 3 node (controller, neutron and compute) Openstack setup, but i'm

Re: [Openstack] VM_MISSING_PV_DRIVERS

Hi Leandro, This is most likely that your compute VM has been created as an HVM guest, rather than a PV guest. This will typically happen if you use the Other Install Media template in XenServer rather than the template for the specific Linux version. The error reported is that we cannot

Re: [Openstack] xenserver and cinder

Hi Ivan, XenAPINFSDriver was primarily useful for pooled scenarios (which in turn relied on Nova aggregates) - however it's not the easiest way to consume Cinder volumes. The XenServer Nova integration supports BFV and volume attach for Cinder volumes presented over iSCSI, so however those

Re: [Openstack] xenserver and cinder

backend for Cinder. Bob From: Ivan Derbenev [mailto:ivan.derbe...@tech-corps.com] Sent: 14 July 2015 16:13 To: Bob Ball; openstack@lists.openstack.org Subject: RE: xenserver and cinder Well, we are migrating from cloudstack now and it has this feature So, do I understand It right. In current

Re: [Openstack] xenserver and cinder

only? What's the use case here? Bob From: Ivan Derbenev [mailto:ivan.derbe...@tech-corps.com] Sent: 14 July 2015 14:50 To: Bob Ball; openstack@lists.openstack.org Subject: RE: xenserver and cinder So, do I understand it right - I can't get rid of additional layer for cinder volumes, if I want

Re: [Openstack] xenserver and cinder

to particular VMs. For example, you create the cinder volumes _before_ you attach it to a virtual machine - so there is no knowledge of which VM or which hypervisor will be attaching to the volume. Bob From: Ivan Derbenev [mailto:ivan.derbe...@tech-corps.com] Sent: 14 July 2015 15:10 To: Bob Ball

Re: [openstack-dev] [nova] Network issue with libvirt-xen driver, iptables race

Hi Anthony, The Xen script is simply calling those commands: ... iptables -I FORWARD -m physdev --physdev-is-bridged --physdev-in $dev -j ACCEPT iptables -I FORWARD -m physdev --physdev-is-bridged --physdev-out $dev -j ACCEPT Are you saying that these two commands aren't needed to be

[openstack-dev] [Nova] [XenAPI] New meeting time

Hi all, To be able to involve some new sub-team members in China, we've moved the meeting times as discussed in the last two XenAPI meetings. The new time is at 0930 UTC, Alternate Wednesdays, with the next meeting at 0930 UTC on 8th July. See you there! Bob

Re: [openstack-dev] [nova] Mellanox CI Issues

-Original Message- From: John Garbutt [mailto:j...@johngarbutt.com] On 5 June 2015 at 15:29, Moshe Levi mosh...@mellanox.com wrote: I talked also with John Garbutt and it seem that the recommendation is to filter only doc and test folders, but still I would like to filter some

Re: [openstack-dev] [nova] xen project retrigger

Hi Gary, It should have been included in the comment - what was the changeset that failed? For reference a recheck can be triggered with xen: recheck Thanks, Bob From: Gary Kotton [mailto:gkot...@vmware.com] Sent: 25 May 2015 16:21 To: OpenStack List Subject: [openstack-dev] [nova] xen

Re: [Openstack] Running Xen VMs on Openstack

Hi Girija, I can’t help with converting XenServer VMs to KVM but can I ask why running XenServer under your OpenStack cloud isn’t considered an option? Clearly there are some differences with VM setup (e.g. the VM may be set up to use a specific disk name which won’t be present if you move to

Re: [openstack-dev] [infra] request to disable xenserver CI account

Sorry all for this breakage; I've been on vacation and didn't set up adequate cover. Thanks for disabling it and we'll let everyone know when the job is ready to start commenting and hopefully voting on changes in the very near future. Regards, Bob

Re: [openstack-dev] [neutron] The future of Xen + OVS support

We certainly care about this but converting the XenServer CI to Neutron+OVS has been hitting a number of issues (notably a few concurrency ones – although there are a few missing features) that we’ve been trying to sort through. I am certainly hoping that we’ll have everything stable enough to

Re: [Openstack] Does Xenserver support cinder volume?

Hi, The XenAPINFS driver has indeed been deprecated from Cinder and is not currently under development. This driver was known broken (some required functionality was missing) and only useful in a very specific use case. The XenAPI nova driver can, of course, attach Cinder drives exposed over

Re: [openstack-dev] [OpenStack-Infra] Devstack error when running g-reg: 401 Unauthorized

This is likely https://launchpad.net/bugs/1415795 which is fixed by https://review.openstack.org/#/c/151506/ Make sure you have the above change in your devstack and it should work again. Bob From: liuxinguo [mailto:liuxin...@huawei.com] Sent: 06 February 2015 03:08 To: OpenStack Development

Re: [openstack-dev] [Neutron] XenAPI questions

Hi, The next meeting will be tomorrow @ 15:00 UTC - We'd love to see you there and we can talk about the CI and Terry's work. We're currently meeting fortnightly and skipped one due to travel, which is why there haven't been minutes recently. Thanks, Bob -Original Message- From:

Re: [openstack-dev] Fwd: Image Upload error while installing devstack on CI slave machine.

Hi Abhishek, This is bug https://launchpad.net/bugs/1415795 introduced by https://review.openstack.org/#/c/142967/ because Swift doesn't use olso.config. The fix is at https://review.openstack.org/#/c/151506/ which has not yet been approved, but if you can cherry-pick it for your CI it should

Re: [Openstack] Can't install domU on Xenserver

Hi John, That’s a very interesting error – one I’ve not seen before personally. A quick way to get up and running is to use the nightly XVAs we build from devstack, see http://downloads.vmd.citrix.com/OpenStack/. The blog explaining how to use these is at

Re: [openstack-dev] [Neutron] XenAPI questions

Hi Yamamoto, XenAPI and Neutron do work well together, and we have an private CI that is running Neutron jobs. As it's not currently the public CI it's harder to access logs. We're working on trying to move the existing XenServer CI from a nova-network base to a neutron base, at which point

Re: [Openstack] Is it possible to use Xenserver with two virtual machines as Compute Node and Network node to set up openstack + neutron network?

Hi Dhanesh, Yes, this should be possible – there is no additional coupling between the compute node and the network node when running with XenServer and as such they can easily be running as two separate virtual machines. In terms of the setup, you might want to look at

Re: [Openstack] openstack + libvirt + xl for xen

Hi Xing, It may be that the dom0 qemu helper process is not running. It seems a very similar issue was tracked down to this on the thread at http://lists.xen.org/archives/html/xen-users/2014-05/msg00134.html Ian C pointed out that this helper process is normally started by the xencommons

Re: [openstack-dev] Info on XenAPI data format for 'host_data' call

Hi Daniel, The following is an example return value from one of my hosts {host_name-description: Default install of XenServer, host_hostname: ciceronicus, host_memory: {total: 17169604608, overhead: 266592256, free: 16132087808, free-computed: 16111337472}, enabled: true, host_capabilities:

Re: [openstack-dev] [infra] recheck no bug and comment

-Original Message- From: Sean Dague [mailto:s...@dague.net] Sent: 25 July 2014 12:36 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [infra] recheck no bug and comment Would that still allow us to only trigger 3rd party CI ? eg if we do 'recheck xenserver' I

Re: [openstack-dev] Devstack (icehouse) - XCP - enable live migration

Hi Afef, There was a regression in Icehouse that broke XenAPI aggregates. This has been fixed in Juno, however we would recommend you use live migrate with block migration (using XCP 1.6 or XenServer 6.2 – which is Free as well now, see

Re: [Openstack] [openstack-dev] Devstack (icehouse) - XCP - enable live migration

Hi Afef, There was a regression in Icehouse that broke XenAPI aggregates. This has been fixed in Juno, however we would recommend you use live migrate with block migration (using XCP 1.6 or XenServer 6.2 – which is Free as well now, see

Re: [Openstack] [xs-devel] Delete the imported VM image to release space -- Sisu

it. Thanks. Sisu On Mon, Jun 16, 2014 at 4:43 AM, Bob Ball bob.b...@citrix.commailto:bob.b...@citrix.com wrote: Nothing should be downloading files to DevStackOSDomU; they get downloaded straight into dom0 when you create an image. Why do you think the missing disk space is related to mysql

Re: [Openstack] [xs-devel] Delete the imported VM image to release space -- Sisu

Nothing should be downloading files to DevStackOSDomU; they get downloaded straight into dom0 when you create an image. Why do you think the missing disk space is related to mysql, or to /var? Bob From: xs-devel-requ...@lists.xenserver.org [mailto:xs-devel-requ...@lists.xenserver.org] On

Re: [Openstack] XenServer domU packages

It seems that this was historically provided by nova-compute-xcp but this does not appear on my installation. Given this is lacking in the Ubuntu packaging, you may need to install Nova from source rather than relying on the packaging. Bob -Original Message- From: Mārtiņš Jakubovičs

Re: [Openstack] [xs-devel] XenSever with OpenStack, Live Migration Error

Hi Sisu, 2014-06-05 16:33:27.509 TRACE nova.api.openstack.compute.contrib.admin_actions File /opt/stack/nova/nova/virt/xenapi/vmops.py, line 1840, in check_can_live_migrate_source 2014-06-05 16:33:27.509 TRACE nova.api.openstack.compute.contrib.admin_actions raise

Re: [Openstack] xenserver-core not working with openstack

...@gmail.com] Sent: 07 April 2014 20:57 To: openstack@lists.openstack.org Cc: Bob Ball; Euan Harris Subject: Re: xenserver-core not working with openstack In addtion, there is an error message when running run.sh in domU. Error: Service n-cpu is not running Thanks, Qin On Mon, Apr 7, 2014 at 3:53 PM

Re: [OpenStack-Infra] Requesting service account

Hi Jeremy, Can we request citrix_xenserver_ci to be moved to the Voting third party CI group please. Nova PTL has confirmed he's happy for the XenServer CI to have voting rights: http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-03-06-14.00.log.html 14:35:41 BobBall In which case

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

Hi David, That's a very strange error - it basically means the node has been used for running a test already (both the first error in run_tests.log about the git repository also existing, and the more fatal error about vif 3 existing) I believe this was my fault - I should have purged all

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

- thanks for letting us know. Bob From: Bob Ball Sent: 23 February 2014 20:29 To: David Kranz; #OpenStack External Email Cc: OpenStack Development Mailing List Subject: RE: [qa] Can't interpret failure from XenServer CI Hi David, That's a very strange error

Re: [openstack-dev] [qa] Can't interpret failure from XenServer CI

...@redhat.com] Sent: 23 February 2014 21:17 To: Bob Ball; #OpenStack External Email Cc: OpenStack Development Mailing List Subject: Re: [qa] Can't interpret failure from XenServer CI On 02/23/2014 03:29 PM, Bob Ball wrote: Hi David, That's a very strange error - it basically means the node has

Re: [openstack-dev] [Nova] Meetup Summary

From: Russell Bryant [rbry...@redhat.com] Sent: 17 February 2014 22:41 To: OpenStack Development Mailing List Subject: [openstack-dev] [Nova] Meetup Summary 5) Driver CI - We talked about the ongoing effort to set up CI for all of the compute drivers. The discussion was mostly a status

Re: [openstack-dev] XenAPI / XCP going away from Debian Ubuntu

Hi Thomas, This means that it will also be impossible to support XCP support in OpenStack, unfortunately (the support for XCP was removed a few months ago because that was blocking migration to Debian testing anyway). Just a quick note - there are two separate issues here which some might

Re: [Openstack] Turn a XenServer AllInOne Node into a Compute Node?

Hi Sisu, You can easily convert a VM running all services in devstack to one running just the services needed for compute (nova-compute and nova-network in the case of the stock method for setting up devstack with XenServer). There is a script at

Re: [openstack-dev] [Nova] Future meeting times

+1 here too - I'd love to be able to attend alternate weeks. Bob -Original Message- From: Gary Kotton [mailto:gkot...@vmware.com] Sent: 18 December 2013 14:36 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] Future meeting times

Re: [Openstack] XenServer support

-Original Message- From: Mārtiņš Jakubovičs [mailto:mart...@hostnet.lv] Sent: 18 December 2013 11:06 To: openstack@lists.openstack.org Subject: [Openstack] XenServer support I want to create small cloud but in testing I faced with many issues and it looks like OpenStack +

Re: [Openstack] Problem with aggregate second host with XenServer

This issue seems to have been fixed by https://review.openstack.org/#/c/15910 - so to get it fixed in your environment, try cherry-picking the change using: git fetch https://review.openstack.org/openstack/nova refs/changes/10/15910/1 git cherry-pick FETCH_HEAD I’ll look at trying to get these

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

-Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: 26 November 2013 19:33 To: OpenStack Development Mailing List Subject: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core I would like to propose that we re-add Dan Prince to the nova-core

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

-Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: 25 November 2013 22:37 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan On 11/25/2013 05:19 PM, Matt Riedemann wrote: I'll play

Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan

-Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: 26 November 2013 13:56 To: openstack-dev@lists.openstack.org Cc: Sean Dague Subject: Re: [openstack-dev] [Nova] Hypervisor CI requirement and deprecation plan On 11/26/2013 04:48 AM, Bob Ball wrote: I

Re: [Openstack] devstack log files

Yes. You should set the SCREEN_LOGDIR and LOGFILE parameters - the former is for all of the services that are started and the latter is for stack.sh itself. Bob -Original Message- From: John Smith [mailto:lbalba...@gmail.com] Sent: 26 November 2013 12:05 To:

Re: [Openstack] Openstack and xen issues.

Hi Alvin, Yes, we typically do expect Nova to be running in a DomU. It's worth checking out http://docs.openstack.org/trunk/openstack-compute/install/yum/content/introduction-to-xen.html just to make sure you've got everything covered there. I say typically because in some configurations

Re: [Openstack] Openstack and xen issues.

November 2013 14:31 To: Bob Ball; openstack@lists.openstack.org Subject: Re: [Openstack] Openstack and xen issues. I have put Openstack on a separate machine to try and separate and isolate the various components I need to work with in the interests of making my debugging easier. This in retrospect may

Re: [Openstack] Ceilometer-collector does not receive anything

Hi, Ceilometer is currently KVM specific. I hope this will get fixed during the icehouse cycle, however ceilometer and XenServer/XCP do not work together quite yet. Bob Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I followed this document:

Re: [openstack-dev] Unable to logging to guest console on XCP/xenserver

The trace below seems to be wanting to access the console log, rather than the VNC console. I believe there is a blog post about how to enable this, but basically you need a cronjob to run in dom0 to rotate the logs. This is because the Xen console logging is not ring-based, and therefore

Re: [Openstack] [openstack-dev] Unable to logging to guest console on XCP/xenserver

The trace below seems to be wanting to access the console log, rather than the VNC console. I believe there is a blog post about how to enable this, but basically you need a cronjob to run in dom0 to rotate the logs. This is because the Xen console logging is not ring-based, and therefore

Re: [openstack-dev] [Neutron] Security groups with XenAPI

Hi Simon, Yes, I believe you are right. We were already planning to discuss this very topic at the XenAPI roadmap session at the summit. Hopefully someone will take on tying up this loose end there. Security group support is the only thing we are aware of that is missing from the XenAPI

Re: [openstack-dev] Setting up compute node on XenServer.

Hi Parikshit, More details can be extracted by setting debug=true in /etc/nova/nova.conf or setting default_log_levels to include nova.virt.xenapi.driver=debug. This is likely to be a mis-configured nova.conf - check

Re: [openstack-dev] [nova] [tempest] [ceilometer] Looking for clarification on the diagnostics API

I'm happy with that approach - again I've not seen any discussions about how this should be done. I've added [tempest] and [ceilometer] tags so we can hopefully get input from the guys involved. Bob From: Gary Kotton [mailto:gkot...@vmware.com] Sent: 13 October 2013 05:21 To: OpenStack

  1   2   >