Paul, you are right that the 'extra_info' should not be in the
os-pci:pci_stats, since it's not part of 'pool-keys' anymore, but I'm not sure
if both 'key1' and 'phys_function' will be part of the pci_stats.
Thanks
--jyh
From: Murray, Paul (HP Cloud) [mailto:pmur...@hp.com]
Sent: Thursday, Marc
> -Original Message-
> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> Sent: Wednesday, March 4, 2015 9:56 AM
> To: Jiang, Yunhong
> Cc: openstack-dev@lists.openstack.org; Xu, Hejie
> Subject: Re: [nova][libvirt] The None and 'none' for CONF.libvirt.
ource/target cpu
model, as the suggestion from Tony, am I right?
Thanks
--jyh
> -Original Message-
> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> Sent: Wednesday, March 4, 2015 6:56 AM
> To: Jiang, Yunhong
> Cc: openstack-dev@lists.openstack.org; Xu, Hejie
> Subj
Hi, Daniel
I'm a bit confused of the None/'none' for CONF.libvirt.cpu_mode. Per my
understanding, None means there is no configuration provided and libvirt will
select the default value based on the virt_type, none means no cpu_mode
information should be provided. For the guest, am I rig
> -Original Message-
> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> Sent: Thursday, January 29, 2015 2:34 AM
> To: Jiang, Yunhong
> Cc: openstack-dev@lists.openstack.org
> Subject: Re: [nova] The libvirt.cpu_mode and libvirt.cpu_model
>
> On Wed, Ja
Hi, Daniel
I recently tried the libvirt.cpu_mode and libvirt.cpu_model when I was
working on cpu_info related code and found bug
https://bugs.launchpad.net/nova/+bug/1412994 . The reason is because with
these two flags, all guests launched on the host will use them, while when host
rep
gt; >
> >All together it looks like pre-datastructure code (if someone remembers
> >that). No data types, no type restrictions, you can assign letter to
> >instruction address and pointer to string to float.
> >
> >Same with current metadata in nova/glance. Raw
er to
> instruction address and pointer to string to float.
>
> Same with current metadata in nova/glance. Raw namespace of key-value
> items without any meaningful restriction and specific expression. It
> gives flexibility, but cause a huge strain on operators.
>
> I think it
Resend because I forgot the [nova] in subject.
Hi,
There are some discussion and disagreement on the requirement from
flavor and image metadata at nova spec https://review.openstack.org/#/c/138937/
and I want to get more input from the community.
When launch a VM, some requirem
Hi,
There are some discussion and disagreement on the requirement from
flavor and image metadata at nova spec https://review.openstack.org/#/c/138937/
and I want to get more input from the community.
When launch a VM, some requirements may come from image metadata and
flavor. T
Hello Nova Community,
Please grant a freeze exception for the nova spec "more image
properties support" at https://review.openstack.org/#/c/138937/ .
The potential changes in nova are limited, affecting only to the
corresponding scheduler filters. Its purpose is to ensure and en
Hi, Daniel's & all,
This is a follow up to Daniel's
http://osdir.com/ml/openstack-dev/2014-10/msg00557.html , "Info on XenAPI data
format for 'host_data' call".
I'm considering to change the compute capability to be a nova object,
with well defined field, the reasons are: a) cur
Hi,
I'd like to ask for a feature freeze exception for the
config-drive-image-property.
The spec has been approved, and the corresponding patch
(https://review.openstack.org/#/c/77027/ ) has been +W three time, but failed
to be merged in the end because of gate issue and conflict on
no
> -Original Message-
> From: Nikola Đipanov [mailto:ndipa...@redhat.com]
> Sent: Tuesday, August 12, 2014 3:22 AM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [Nova] Concerns around the Extensible Resource
> Tracker design - revert maybe?
>
> Hey Nova-istas,
>
> W
#x27;m working
on fixing it.
--jyh
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Tuesday, June 10, 2014 1:46 PM
To: Jiang, Yunhong; He, Yongli
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev][nova][pci] A couple of questions
Hi Yunhong
Hi, Nick,
For “have a test case which can be verified using a an OpenSource
implementation ….. ensure that tests can be done without any special hardware
or proprietary software”, I totally agree the requirement for without
proprietary software, however, I’m not sure about your exact meaing of
>
> This is why there is a distinction between properties set on images
> vs properties set on flavours. Image properties, which a normal user
> can set, are restricted to aspects of the VM which don't involve
> consumption of compute host resources. Flavour properties, which
> only a user with 'f
> -Original Message-
> From: Solly Ross [mailto:sr...@redhat.com]
> Sent: Tuesday, May 06, 2014 10:16 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] [Heat] Custom Nova Flavor creation
> through Heat (pt.2)
>
> For your first qu
.
>
> I hope to add our special filter like "nova/pci/PciHostDevicesWhiteList.py".
> So we hope to add a mechanism to specify which filter to use for getting
> the
> pci devices from host.
>
> Best regards to you.
> Ricky
>
> > -Original Message-
> > From: Ji
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Tuesday, May 06, 2014 10:44 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Question about addit log in
> nova-compute.log
>
> On 05/06/2014 01:37
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Monday, May 05, 2014 6:19 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Question about addit log in
> nova-compute.log
>
> On 05/05/2014 04:19
Hi, all
The trusted messaging
(https://blueprints.launchpad.net/oslo.messaging/+spec/trusted-messaging) has
been removed from icehouse, does anyone know how is current status? I noticed a
summit session may cover it (
http://junodesignsummit.sched.org/event/9a6b59be11cdeaacfea70fef34328
Hi, all
Currently I'm working on spec at https://review.openstack.org/#/c/90172/4
which return the status of the hypervisor node. Per the comments, including
comments from operator, this is a welcome features. As in
https://review.openstack.org/#/c/90172/4/specs/juno/return-status-for-hyperv
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Monday, May 05, 2014 9:50 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Question about addit log in
> nova-compute.log
>
> On 05/04/2014 11:09 PM, Chen CH Ji wrote:
> > Hi
> >
Hi, Bohai, are you talking about the scheduler filter for PCI, right?
I think the scheduler filters can be changed by nova options already, so I
don't think we need another mechanism and just create another filter to replace
the default pci filter?
--jyh
> -Original Message-
> From: Bo
-dev] How to add a property to the API extension?
>
> On 2014年04月17日 05:25, Jiang, Yunhong wrote:
> > Hi, Christopher,
> > I have some question to the API changes related to
> https://review.openstack.org/#/c/80707/4/nova/api/openstack/compute/
> plugins/v3/hypervisors.py
Hi, Christopher,
I have some question to the API changes related to
https://review.openstack.org/#/c/80707/4/nova/api/openstack/compute/plugins/v3/hypervisors.py
, which adds a property to the hypervisor information.
a) I checked the https://wiki.openstack.org/wiki/APIChangeGuidelines bu
> single comment they made was -1 worthy on its own. Often times I will -1
> for a spelling mistake and then make a bunch of other purely-opinion
> comments which don't necessarily need to change.
Do we really want to -1 for spelling mistake in nova-specs? This is really a
bad news for non-native
Sorry forgot nova prefix in subject.
--jyh
> -Original Message-
> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> Sent: Friday, February 28, 2014 9:32 PM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] Some changes on config drive
>
>
-ATTR:host
>
> On 02/28/2014 11:38 AM, Jiang, Yunhong wrote:
> > One reason of the confusion is, in some virt driver (maybe xenapi or
> > vmwareapi), one compute service manages multiple node.
>
> Okay, so in the scenario above, is the nova-compute service running on a
I thi
Hi, Michael and all,
I created some changes to config_drive, and hope to get some feedback.
The patches are at
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:config_drive_cleanup,n,z
The basically ideas of the changes are:
1) In
One reason of the confusion is, in some virt driver (maybe xenapi or
vmwareapi), one compute service manages multiple node.
--jyh
> -Original Message-
> From: Chris Friesen [mailto:chris.frie...@windriver.com]
> Sent: Friday, February 28, 2014 7:40 AM
> To: openstack-dev@lists.openstack.
? Or, take image property as precendence.
Thanks
--jyh
> -Original Message-
> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> Sent: Thursday, February 27, 2014 1:55 PM
> To: OpenStack Development Mailing List (not for usage questions);
> yunhong jiang
&
Hi, Michael, I created a bug at https://bugs.launchpad.net/nova/+bug/1285880
and please have a look.
Thanks
--jyh
> -Original Message-
> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> Sent: Thursday, February 27, 2014 1:35 PM
> To: OpenStack Development Mailing L
> -Original Message-
> From: Michael Still [mailto:mi...@stillhq.com]
> Sent: Thursday, February 27, 2014 1:04 PM
> To: yunhong jiang
> Cc: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [Nova] why force_config_drive is a per
> comptue node config
>
> On Fri, Feb 28, 2
Hi, Brian
I created the BP for persistent resource claim at
https://blueprints.launchpad.net/nova/+spec/persistent-resource-claim , based
on the discussion on IRC, can you please have a look on it to see any potential
issue?
Thanks
--jyh
__
Hi, John and all,
I updated the blueprint
https://blueprints.launchpad.net/nova/+spec/pci-extra-info-icehouse according
to your feedback, to add the backward compatibility/upgrade issue/examples.
I try to separate this BP with the SR-IOV NIC support as a standalone
enhancement,
Robert, thanks for your long reply. Personally I'd prefer option 2/3 as it keep
Nova the only entity for PCI management.
Glad you are ok with Ian's proposal and we have solution to resolve the libvirt
network scenario in that framework.
Thanks
--jyh
> -Original Message-
> From: Robert
track additional resource data.
>
> Paul.
>
> -Original Message-
> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> Sent: 17 January 2014 05:54
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] how is resou
There are some related discussion on this before.
There is a BP at
https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking which
try to support more resources.
And I have a documentation at
https://docs.google.com/document/d/1gI_GE0-H637lTRIyn2UPfQVebfk5QjDi6ohObt6MIc0
. My
I noticed the BP has been approved, but I really want to understand more on the
reason, can anyone provide me some hints?
In the BP, it states that "For resize, we need to confirm, as we want to give
end user an opportunity to rollback". But why do we want to give user an
opportunity to rollbac
> -Original Message-
> From: Dan Smith [mailto:d...@danplanet.com]
> Sent: Monday, January 13, 2014 6:35 AM
> To: Jiang, Yunhong; Murray, Paul (HP Cloud Services) (pmur...@hp.com)
> Cc: openstack-dev@lists.openstack.org
> Subject: Re: The extra_resource in compute node
shouldn't be
an excessive number of pci_stats pools. I am not going to stand up and say
this makes it achievable - and if it doesn't them I'm not sure that anything
would make overlapping flavors achievable - but I think it gives us some hope.
--
Ian.
On 13 January 2
2:51 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Jiang, Yunhong; He, Yongli; Robert Li (baoli) (ba...@cisco.com); Sandhya
Dasu (sadasu) (sad...@cisco.com); ijw.ubu...@cack.org.uk; j...@johngarbutt.com
Subject: RE: [openstack-dev] [nova] [neutron] PCI pass-through netwo
Hi, Robert, scheduler keep count based on pci_stats instead of the pci flavor.
As stated by Ian at
https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg13455.html
already, the flavor will only use the tags used by pci_stats.
Thanks
--jyh
From: Robert Li (baoli) [mailto:ba...@cisco
Comments with prefix [yjiang5_2] , including the double confirm.
I think we (you and me) is mostly on the same page, would you please give a
summary, and then we can have community , including Irena/Robert, to check it.
We need Cores to sponsor it. We should check with John to see if this is
di
00:04, Jiang, Yunhong
mailto:yunhong.ji...@intel.com>> wrote:
[yjiang5] Really thanks for the summary and it is quite clear. So what's the
object of "equivalent devices at host level"? Because 'equivalent device * to
an end user *" is flavor, so is it 'equiv
Hi, Paul/Dan
For the extra_resource (refer to Dan's comments in
https://review.openstack.org/#/c/60258/ for more information), I created a
patch set
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:extra_resources,n,z
and want to get some feedback.
Ian, thanks for your reply. Please check comments prefix with [yjiang5].
Thanks
--jyh
From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: Friday, January 10, 2014 12:17 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-thr
Brian, the issue of 'class name' is because currently the libvirt does not
provide such information, otherwise we are glad to add that :(
But this is a good point and we have considered already. One solution is to
retrieve it through some code like read the configuration space directly. But
that
ss-through network support
On 10 January 2014 07:40, Jiang, Yunhong
mailto:yunhong.ji...@intel.com>> wrote:
Robert, sorry that I'm not fan of * your group * term. To me, *your group"
mixed two thing. It's an extra property provided by configuration, and also
it's a v
BTW, I like the PCI flavor :)
From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
Sent: Thursday, January 09, 2014 10:41 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-through network support
Hi, Ian, when you in
Hi, Ian, when you in aggrement with all of this, do you agree with the 'group
name', or agree with John's pci flavor?
I'm against the PCI group and will send out a reply later.
--jyh
From: Ian Wells [mailto:ijw.ubu...@cack.org.uk]
Sent: Thursday, January 09, 2014 9:47 AM
To: OpenStack Developmen
roperty, how to select/group devices based on the
property, how to store/fetch these properties.
Thanks
--jyh
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Thursday, January 09, 2014 8:49 AM
To: OpenStack Development Mailing List (not for usage questions); Irena
Berezovsky; Sandhya Dasu
bly going to split some of
> the tasks up into different bps (at the suggestion of Dan and Russell).
>
> Is there a particular part you were interested in?
>
> -Original Message-
> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> Sent: 14 November 2013 18:20
>
> -Original Message-
> From: Dan Smith [mailto:d...@danplanet.com]
> Sent: Friday, November 15, 2013 7:30 AM
> To: OpenStack Development Mailing List (not for usage questions);
> isaku.yamah...@gmail.com
> Subject: Re: [openstack-dev] [nova][api] Is this a potential issue
>
> > You're no
>
> The migration shouldn't end up being set to 'reverting' twice because of
> the expected_task_state set and check in
> instance.save(expected_task_state=None). The quota reservation could
> happen twice, so a rollback in the case of a failure in instance.save
> could be good.
A patch uploaded
> -Original Message-
> From: Dan Smith [mailto:d...@danplanet.com]
> Sent: Thursday, November 14, 2013 10:43 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova][object] One question to the resource
> tracker session
>
> >> You're ri
t; tracker session
>
> On 11/14/13 at 05:37pm, Jiang, Yunhong wrote:
> >
> >> -Original Message-
> >> From: Andrew Laski [mailto:andrew.la...@rackspace.com]
> >> Sent: Wednesday, November 13, 2013 3:22 PM
> >> To: OpenStack Development Mailing List
t; tracker session
>
> On 11/13/13 at 11:12pm, Jiang, Yunhong wrote:
> >Hi, Dan Smith and all,
> > I noticed followed statement in 'Icehouse tasks' in
> https://etherpad.openstack.org/p/IcehouseNovaExtensibleSchedulerMetr
> ics
> >
> > c
Hi, Dan Smith and all,
I noticed followed statement in 'Icehouse tasks' in
https://etherpad.openstack.org/p/IcehouseNovaExtensibleSchedulerMetrics
convert resource tracker to objects
make resoruce tracker extensible
no db migrations ever
> -Original Message-
> From: Chris Friesen [mailto:chris.frie...@windriver.com]
> Sent: Wednesday, November 13, 2013 9:57 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Core pinning
>
> On 11/13/2013 11:40 AM, Jiang, Yunhong wro
> -Original Message-
> From: Tuomas Paappanen [mailto:tuomas.paappa...@tieto.com]
> Sent: Wednesday, November 13, 2013 4:46 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [nova] Core pinning
>
> Hi all,
>
> I would like to hear your thoughts about core pinning in
> -Original Message-
> From: Shawn Hartsock [mailto:hartso...@vmware.com]
> Sent: Tuesday, November 12, 2013 12:56 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] [heat] Custom Flavor creation through
> Heat
>
> My concern with
n 11/11/13 at 05:27pm, Jiang, Yunhong wrote:
> >Resend after the HK summit, hope someone can give me hint on it.
> >
> >Thanks
> >--jyh
> >
> >> -Original Message-
> >> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> >> Sent:
Resend after the HK summit, hope someone can give me hint on it.
Thanks
--jyh
> -Original Message-
> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> Sent: Thursday, November 07, 2013 5:39 PM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [nova]
Hi, all
I'm a bit confused of followed code in ./compute/api.py, which will be
invoked by api/openstack/compute/servers.py, _action_revert_resize().
From the code seems there is a small windows between get the migration
object and update migration.status. If another API request c
Bryant [mailto:rbry...@redhat.com]
> Sent: Sunday, November 03, 2013 12:12 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova][scheduler]The database access in the
> scheduler filters
>
> On 11/01/2013 06:39 AM, Jiang, Yunhong wrote:
>
Aha, right after replied Harsock's mail, I realized I'm correct still. Glad
that I did graduated from the school :)
--jyh
> -Original Message-
> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> Sent: Friday, November 01, 2013 10:32 AM
> To: OpenStack Develop
Shawn, yes, there is 56 VM access every second, and for each VM access, the
scheduler will invoke filter for each host, that means, for each VM access, the
filter function will be invoked 10k times.
So 56 * 10k = 560k, yes, half of 1M, but still big number.
--jyh
> -Original Message-
>
Yes, you are right .. :(
> -Original Message-
> From: Shawn Hartsock [mailto:hartso...@vmware.com]
> Sent: Friday, November 01, 2013 8:20 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova][scheduler]The database access in the
> s
As Shawn Hartsock pointed out in the reply, I made a stupid error in the
calculation. It's in fact 55 access per second, not that big number I
calculated.
I thought I graduated from elementary school but seems I'm wrong. Really sorry
for the stupid error.
--jyh
> -Original Message-
>
I noticed several filters (AggregateMultiTenancyIsoaltion, ram_filter,
type_filter, AggregateInstanceExtraSpecsFilter) have DB access in the
host_passes(). Some will even access for each invocation.
Just curios if this is considered a performance issue? With a 10k nodes, 60 VM
per node, and 3 h
[neutron] PCI pass-through network
> support
>
> Hi Yunhong.
>
> On Tue, Oct 29, 2013 at 08:22:40PM +,
> "Jiang, Yunhong" wrote:
>
> > > * describe resource external to nova that is attached to VM in the API
> > > (block device mapping and/or v
On Tue, Oct 29, at 4:31 pm, Jiang, Yunhong
> wrote:
>
> > Henry,why do you think the "service VM" need the entire PF instead of a
> > VF? I think the SR-IOV NIC should provide QoS and performance
> isolation.
>
> I was speculating. I just thought it might be
er 802.1Qbg or 802.1Qbh, but configured locally by Neutron
> Agent. We
> > also support both Ethernet and InfiniBand physical network L2
> technology.
> > This means that we apply different configuration commands to set
> > configuration on VF.
> >
> >
>
ement.
Instead, the PCI requirement should come from the network configuration and
image property. Or you think user still need passing flavor with pci request?
--jyh
From: Irena Berezovsky [mailto:ire...@mellanox.com]
Sent: Tuesday, October 29, 2013 3:17 AM
To: Jiang, Yunhong; Robert Li (bao
er to obtain it.
> >
> > * It can be done by having a dedicated L2 neutron agent on
> each
> > Host that scans for allocated PCI devices and then retrieves networking
> > configuration from the server and configures the device. The agent will
> be
> > a
n?
Thanks
--jyh
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Monday, October 28, 2013 12:22 PM
To: Irena Berezovsky; prashant.upadhy...@aricent.com; Jiang, Yunhong;
chris.frie...@windriver.com; He, Yongli; Itzik Brown
Cc: OpenStack Development Mailing List; Brian Bowen (brbowen); Ky
Hi, stackers,
When reading code related to the resource tracker, I noticed AggregateRamFilter
as in https://review.openstack.org/#/c/33828/.
I'm not sure if it's better to use per node configuration of ram ration,
instead of depends on the host aggregate? Currently we have to have DB call for
I thought it will be used when use local environment for ./run_test.sh,
but./run_test.sh -N will have several failure and seems not supported anymore.
Thanks for any input/suggestions.
--jyh
> -Original Message-
> From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com]
> Sent
Hi, stackers,
I have a question to followed code in
nova/tests/virt/libvirt/test_libvirt.py. My question is, when will the 'import
libvirt' success and the fake libvirt not used?
try:
import libvirt
except ImportError:
import nova.tests.virt.libvirt.fakelibvirt as libvirt
libvirt
IMHO, this seems fit better of the availability since location is more about
availability like power supply, network switch availability etc.
Or, what's the boundary of host aggregate and availability zone? Seems host
aggregate is so magic that it can cover every requirement to separate/group th
I created a wiki page at https://wiki.openstack.org/wiki/Pci_passthrough , and
I think Irena has updated it also.
Thanks
--jyh
> -Original Message-
> From: David Kang [mailto:dk...@isi.edu]
> Sent: Friday, September 13, 2013 1:07 PM
> To: OpenStack Development Mailing List
> Subject: Re:
Sorry for slow response, I'm out of office to IDF, I will have a look on it
today.
Thanks
--jyh
> -Original Message-
> From: David Kang [mailto:dk...@isi.edu]
> Sent: Wednesday, September 11, 2013 6:11 AM
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [nova] [pci
Gary
Firstly, thanks for your review very much.
The pci_stats is calculated in the resource tracker in the compute
node and is also saved in compute_node, I think currently the scheduler depends
on the information provided by the compute_node table so this method should fit
int
> -Original Message-
> From: Michael Still [mailto:mi...@stillhq.com]
> Sent: Tuesday, August 27, 2013 7:45 PM
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [Nova] Frustrations with review wait times
>
> [Concerns over review wait times in the nova project]
>
>
Hi, Boris
I'm a surprised that you want to postpone the PCI support
(https://blueprints.launchpad.net/nova/+spec/pci-passthrough-base) to I
release. You and our team have been working on this for a long time, and the
patches has been reviewed several rounds. And we have been waiting for
The thing laggy is, currently resource tracker will update the usage
information whenever resource changes, not only in periodic tasks. If you
really want to get the current result with periodic update, you have to do some
in-memory management and you even need sync between different scheduler
ease raise it and we will
enhance our resource tracker for this. That's not complex task.
Thanks
--jyh
> -Original Message-
> From: Russell Bryant [mailto:rbry...@redhat.com]
> Sent: Monday, July 22, 2013 8:22 AM
> To: Jiang, Yunhong
> Cc: bo...@pavlovic.me; ope
lovic
Mirantis Inc.
On Fri, Jul 19, 2013 at 11:23 PM, Jiang, Yunhong
mailto:yunhong.ji...@intel.com>> wrote:
Boris
I think you in fact covered two topic, one is if use db or rpc for
communication. This has been discussed a lot. But I didn't find the conclusion.
From the d
Boris
I think you in fact covered two topic, one is if use db or rpc for
communication. This has been discussed a lot. But I didn't find the conclusion.
From the discussion, seems the key thing is the fan out messages. I'd suggest
you to bring this to scheduler sub meeting.
http://eaves
92 matches
Mail list logo