Hi Dietmar,
On Wed, Jan 15, 2014 at 12:43 AM, Dietmar Maurer wrote:
> What timeout woul you suggest?
>
In order to reduce initial user frustration especially on slower devices, I
would make it 40 seconds if you're comfortable with such a timeout. An
experienced user with a fast device probably n
> Thanks for confirming the functionality! Do you guys think it's warranted to
> extend the timeout a bit so that people who are not as fast at realizing they
> have to tap on the downloaded file will have time? Check how soon the ticket
> expires subjectively and tell me whether you feel in a rush
Hi Martin,
On Tue, Jan 14, 2014 at 4:38 AM, Martin Maurer wrote:
> I just got it running on my Nexus 7 (first version), running on current
> android 4.4.2 and using Chrome Browser.
>
Thanks for confirming the functionality! Do you guys think it's warranted
to extend the timeout a bit so that pe
>>applied.
>>But I simply use a normal button instead of the split button.
>>Turned out to be easier to use. We can still optimize that in future.
Ok, works fine here. Thanks !
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre Derumier" , pve-devel@pve.proxmox.com
Envoyé: Mar
>>OK, will update that to 128
Thanks. I use myself quad amd servers (4x16cores).
and with hotplug, we can only use 1 socket. That's why I have put 64cores max.
(Don't known if bigger server exist, but 128 seem to be fine).
- Mail original -
De: "Dietmar Maurer"
À: "Stefan Priebe - P
applied.
But I simply use a normal button instead of the split button.
Turned out to be easier to use. We can still optimize that in future.
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre Derumier
> Sent:
OK, will update that to 128
> -Original Message-
> From: Stefan Priebe - Profihost AG [mailto:s.pri...@profihost.ag]
> Sent: Dienstag, 14. Jänner 2014 10:54
> To: Dietmar Maurer; Alexandre Derumier; pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] [PATCH 1/2] qemu processor : update ma
a max of 32 cores seems to be generally to low. I already have raised it
locally to 128.
Think of current AMD Quad core machines.
Stefan
Am 14.01.2014 10:48, schrieb Dietmar Maurer:
> This was removed from your second series - do we need this?
>
>> -Original Message-
>> From: pve-devel
This was removed from your second series - do we need this?
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre Derumier
> Sent: Montag, 06. Jänner 2014 17:59
> To: pve-devel@pve.proxmox.com
> Subject: [pve-de
applied part 1 and 2 - thanks!
> -Original Message-
> From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel-
> boun...@pve.proxmox.com] On Behalf Of Alexandre DERUMIER
> Sent: Montag, 13. Jänner 2014 10:17
> To: pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] qemu-server : add cpu
Hi,
I just got it running on my Nexus 7 (first version), running on current android
4.4.2 and using Chrome Browser.
The Proxmox VE gui is unusable slow on this device but basically it works and
the SPICE connection opens as described in your post, great!
There is already a third party Android A
>>There is only one API, and command line tools also use that API.
>>
>>So that change would disable it for GUI and CLI.
Ok, any idea how to implement this easily ?
It could be great to have a central entry point where whe can check if we can
change or not values online.
- Mail original
> Another thing I can say is that both the Admin portal of oVirt and Proxmox
> have
> relatively small buttons which are well suited to clicking with a mouse but
> not
> for tapping on a mobile device. Also, having one side of the (Shell) button as
> drop-down functionality looks very good and wo
13 matches
Mail list logo
