Thomas, H. and Bob,
Please note only the scripts under "os_xenapi/dom0/etc/xapi.d/plugins/" will
run in dom0 only. During deployment an OpenStack environment, we usually copy
the plugins into dom0 from the installed package (installed in DomU). In this
way, it helps us to ensure the plugins
: Mon, 25 Sep 2017 14:51:46 +0700
From: Adhi Priharmanto <adhi@gmail.com>
To: Jianghua Wang <jianghua.w...@citrix.com>
Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>
Subject: Re: [Openstack] FW: [xenserver-ocata] ceilometer compute
error
Jianghua Wang would like to recall the message, "[Openstack] [xenserver-ocata]
ceilometer compute".
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscr
: Mon, 25 Sep 2017 14:51:46 +0700
From: Adhi Priharmanto <adhi@gmail.com>
To: Jianghua Wang <jianghua.w...@citrix.com>
Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>
Subject: Re: [Openstack] FW: [xenserver-ocata] ceilometer compute
error
lavors. Basically most of the logic is already implemented and
> > > the method 'consume_request' is going to select the right vGPUs
> > > according the request.
> > >
> > > In /virt we will have to:
> > >
> > > * Update the field 'pci_pa
ecking the code line from the log, it’s probably already
in pike.
Regards,
Jianghua
From: wjh_fresh [mailto:wjh_fr...@163.com]
Sent: Monday, September 11, 2017 1:38 PM
To: Jianghua Wang <jianghua.w...@citrix.com>
Subject: Fw: [Openstack] [xenserver-ocata] ceilometer compute error
Rrd_interf
Ruijing,
I'm not sure about other cases, but XenServer CI is using nested
virtualization.
Regards,
Jianghua
From: Guo, Ruijing [mailto:ruijing@intel.com]
Sent: Tuesday, February 28, 2017 4:52 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev]
Thanks Ihar, Thierry and Bob. I think we've agreed to go with the 1st option -
"Get Neutron to call XenAPI directly rather than trying to use a daemon".
I will refine the POC patch to make it ready for the formal review.
R.g.t the test, I did some basic test in a real lab manually and it worked
ire any changes per-project.
>
> With the change of direction from oslo.roowrap to oslo.provsep I doubt that
> there is scope to land this in oslo.rootwarp.
>
> Yours Tony.
>
> -Original Message-
> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
> Sent: Tuesday, Novembe
Thanks Thierry.
Is Neutron ready to switch oslo.rootwrap to oslo.privsep?
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. All of the commands to be
executed are sent to the common dom0 XAPI daemon (which will
ootwrap problem
for XenServer
Jianghua Wang <jianghua.w...@citrix.com> wrote:
> Hi Neutron guys,
>
> I’m trying to explain a problem with the XenServer rootwrap and give a
> proposal to resolve it. I need some input on how to proceed with this
> proposal: e.g. if requir
Hi Neutron guys,
I'm trying to explain a problem with the XenServer rootwrap and give a proposal
to resolve it. I need some input on how to proceed with this proposal: e.g. if
requires a spec? Any concerns need further discussion or clarification?
Problem description:
As we've known, some
To: OpenStack Development Mailing List (not for usage questions); Jianghua Wang
Subject: 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?
Added project prefix in the subject and loop in Masayuki and Ghanshyam who know
the background as well. Thanks.
Jianghua
From: Jianghua Wang
Sent: Tuesday, June 14, 2016 12:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Jianghua Wang
Subject: Discussion on to enable
Hi all,
Recently the "Citrix XenServer CI" was broken due to a bad commit[1] to
openstack/tempest. As the commit was merged on Friday which is vacation at
here, it had been in failure for more than three days before we noticed and
fixed[2] this problem. As this CI votes for openstack/nova,
tive ports as the subsidiary part to the active port. And add
function to sync the configuration to inactive ports once any update on the
active port.
Any comments are welcome and appreciated.
Thanks,
Jianghua
-Original Message-
Date: Mon, 12 Oct 2015 16:12:23 +0000
From: Jianghua Wang &
ort switch to vifx.0; but depending on the neutron agent
polling interval, the vifx.0 may not be tagged for a while; then during this
period the connection is lost.
Could you share your insights? Thanks a lot.
B.R.
Jia
17 matches
Mail list logo
