, HPservers-Core-OE-PSC) chuan.l...@hp.com
To: Gilad Chaplik gchap...@redhat.com
Cc: Sven Kieske s.kie...@mittwald.de, devel@ovirt.org
Sent: Wednesday, May 28, 2014 5:14:39 AM
Subject: RE: [ovirt-devel] Discussion VM CPU pinning and NUMA CPU pinning
The patch is already upload yesterday
...@mittwald.de, devel@ovirt.org
Sent: Tuesday, May 27, 2014 5:08:55 AM
Subject: Re: [ovirt-devel] Discussion VM CPU pinning and NUMA CPU pinning
Yes, you are right.
And this design is almost like the libvirt capabilities format
cpu id='0' socket_id='0' core_id='0' siblings='0'/ with attribute
Kieske; devel@ovirt.org
Subject: Re: [ovirt-devel] Discussion VM CPU pinning and NUMA CPU pinning
Hi Jason,
I guess that the time you've waited for feedback is sufficient.
please upload a patch as described (I hope I will get it merged tomorrow).
Thanks,
Gilad.
- Original
Hi All,
After discussion with some community members, we are supposed to make some
conclusion of this topic.
Change API model object on api.xsd
1. remove NumaCPU and NumaCPUs from NumaNode and VirtualNumaNode.
2. add Core and Cores under the CPU to show the CPU topology details.
3. add the CPU
- Original Message -
From: Chuan Liao (Jason Liao, HPservers-Core-OE-PSC) chuan.l...@hp.com
To: Gilad Chaplik gchap...@redhat.com
Cc: devel@ovirt.org, Doron Fediuck dfedi...@redhat.com, Martin Sivák
msi...@redhat.com, Juan Hernandez
juan.hernan...@redhat.com, Malini Rao
Can you please be more specific on how to model RESTful API, with regards to
CPU and CPU-pinning.
Thanks,
Gilad.
- Original Message -
From: Chuan Liao (Jason Liao, HPservers-Core-OE-PSC) chuan.l...@hp.com
To: devel@ovirt.org
Cc: Doron Fediuck dfedi...@redhat.com, Gilad Chaplik
