Hi Gilad,
The restful API model of NUMA CPU and CPU-pinning is named NUMACPU ( Under
NumaNode, VirutalNumaNode )
Which is contain some attributes;
index (xs:int): Numa CPU index or vNuma CPU index.
pin_set (xs:string): Virtual NUMA CPU pin to host NUMA CPU set. ( only enabled
on VirtualNumaNode
Hi Gilad,
Thanks for your reply. Did you submit the UI code. We need to know your UI
model to consolidate your feedback. Meanwhile, we need to know the current cpu
pining solution that include the UI code you are in charging. Then, we will see
if we can specific to RESTful.
Best Regards,
David
- Original Message -
> From: "Eli Mesika"
> To: "Yair Zaslavsky"
> Cc: devel@ovirt.org
> Sent: Thursday, May 15, 2014 4:56:50 PM
> Subject: Re: [ovirt-devel] Entity names in DB scripts
>
>
>
> - Original Message -
> > From: "Yair Zaslavsky"
> > To: devel@ovirt.org
> > Sent:
On Thu, May 15, 2014 at 05:21:48PM +0200, Matthias Runge wrote:
> On Thu, May 15, 2014 at 10:15:33AM +0100, Dan Kenigsberg wrote:
> > > This update is pushed to updates-testing (for f20), though due the system
> > > maintenance currently running, there was no mail sent about that.
> > > Please leav
- Original Message -
> From: "Greg Sheremeta"
> To: devel@ovirt.org
> Sent: Thursday, May 15, 2014 10:56:10 AM
> Subject: [ovirt-devel] spacing fix with PatternFly and tables
>
> Hi,
>
> With the PatternFly look and feel patch applied, GWT's spacing attribute is
> no longer reliable. Wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, May 15, 2014 at 10:15:33AM +0100, Dan Kenigsberg wrote:
> > This update is pushed to updates-testing (for f20), though due the system
> > maintenance currently running, there was no mail sent about that.
> > Please leave feedback on bodhi. Than
Hi,
With the PatternFly look and feel patch applied, GWT's spacing attribute is no
longer reliable. When GWT renders a table with this, it puts "cellspacing='10'"
into the table. This no longer works, probably because we changed to border-box
model.
The alternative:
.some-table {
border-sp
- Original Message -
> From: "Eli Mesika"
> To: "Yair Zaslavsky"
> Cc: devel@ovirt.org
> Sent: Thursday, May 15, 2014 4:56:50 PM
> Subject: Re: [ovirt-devel] Entity names in DB scripts
>
>
>
> - Original Message -
> > From: "Yair Zaslavsky"
> > To: devel@ovirt.org
> > Sent: Th
- Original Message -
> From: "Yair Zaslavsky"
> To: devel@ovirt.org
> Sent: Thursday, May 15, 2014 3:20:18 PM
> Subject: [ovirt-devel] Entity names in DB scripts
>
> Hi all,
> I have a feeling there is some inconsistency in using entity names in the DB
> scripts.
> For example, should w
Hi Federico,
I agree with you, the 2 patched are now squashed. I left the unit test
aside since it requires some additional review. I'm without free time
to spend on this since I'm in the middle of a life change (new work +
new country), so I wrote it very quickly.
Kind regards
Enrico
On Tue, Ma
Hi all,
I have a feeling there is some inconsistency in using entity names in the DB
scripts.
For example, should we use Host or VDS?
I am not talking about existing tables or columns but about new ones (and new
stored procedures).
I am quite sure I saw patches containing both approaches.
Yair
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)"
> To: devel@ovirt.org
> Cc: "Doron Fediuck" , "Gilad Chaplik"
> , "Martin Sivák" ,
> "Juan He
Hi All,
Now we are working on the NUMA tune feature development for oVirt 3.5. This
feature allow user to configure the vCPU pining according to host CPU/NUMA
topology to get the best performance for created VM. But this will impact the
current function of vCPU pining. Now, we are looking for a
- Original Message -
> From: "Einav Cohen"
> To: "Greg Sheremeta"
> Cc: "Vojtech Szocs" , "Alexander Wels" ,
> devel@ovirt.org
> Sent: Thursday, May 15, 2014 3:22:53 AM
> Subject: Re: [ovirt-devel] limiting gwt compiler threads to 1
>
> I could be wrong, but it seems that the default
Hi Greg,
I assume you're developing against the master branch.
Your "make" command looks good, note that ThreadedPermutationWorkerFactory
is already applied [1] so there's no need to specify that in build command.
To use max. 1 thread for GWT compilation, try this:
$ make ... DEV_EXTRA_BUILD_
On Wed, May 14, 2014 at 04:33:13PM +0200, Matthias Runge wrote:
> On Tue, May 13, 2014 at 06:15:31PM -0300, Amador Pahim wrote:
> > >>
> > >> I'm using python-pep8-1.5.4-1.fc20.noarch
> > >
> > > It seems like a bug in pep8 tool, and I see that it does not reproduce
> > > with v1.5.6 thereof.
> > >
16 matches
Mail list logo
