> This approach is not optimal, because the changelog does not mention
> that this is just a copy of the original file. We need to make that more
> clear. I see two way to do that:
>
> A.) Use special commit message 'copy file to manager5' (something like that)
> (The commit should not contain oth
OK, I finally commited this change, but modified the
commit message header to:
"copy Utils.js from manager to manager5"
hope that is OK for you?
On 04/14/2015 01:28 PM, Emmanuel Kasper wrote:
Developement of the ext5 version of the pve-manager will take place
in the www/management5 directory
> Developement of the ext5 version of the pve-manager will take place
> in the www/management5 directory of the git repo.
> We start the initial import with Utils.js, who contains variables and
> static functions used by all other components.
This approach is not optimal, because the changelog doe
Hi,
On 14/04/15 09:44, Eneko Lacunza wrote:
On 13/04/15 18:24, Dietmar Maurer wrote:
Otherwise a change to the parameters from
the GUI can reset the hand-set MTU in /etc/network/interfaces
We never reset parameters like MTU. Do you can a test case?
I can change anything from GUI, without overw
Alexandre,
> Am 14.04.2015 um 08:44 schrieb Alexandre DERUMIER :
>
>>> Any idea what the upgrade / migration path from the older firefly release
>>> might look like?
>
> I have upgrade my current proxmox cluster (3.4) from firefly->giant->hammer,
> but firefly->hammer is working too.
>
> It's
Developement of the ext5 version of the pve-manager will take place
in the www/management5 directory of the git repo.
We start the initial import with Utils.js, who contains variables and
static functions used by all other components.
Signed-off-by: Emmanuel Kasper
---
www/manager5/Utils.js | 10
For ext 5 developpment, we will include in the html headers every javascript
ressources
incrementally, so we can bypass the "make install" step.
Signed-off-by: Emmanuel Kasper
---
PVE/ExtJSIndex5.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/ExtJSIndex5.pm b/PVE/Ext
Provided you symlink the manager5 directory to your git repository,
this will allow to test javascript changes by simply reloading
the page, without calling "make install" in between.
For instance, if you have your pve-manager code in $HOME/pve/pve-manager,
you can do
ln -s $HOME/pve/pve-manager/w
>>Just to keep things easy...
Ok.
Looking at hammer release, it seem that currently it can be only defined on rbd
volume creation.
But a new patch in ceph master allow to change it on the fly.
I have sent a mail to the ceph mailing to see if it'll be backported to hammer
soon.
- Mail o
> On April 14, 2015 at 11:59 AM Emmanuel Kasper wrote:
>
>
> Hello !
> I am involved at the moment in the migration of our Javascript code base
> from Ext Js 4 to Ext JS 5, and I would like to start it doing with the
> following approach:
>
> * create a manager5/ directory
> * copy incr
Hello !
I am involved at the moment in the migration of our Javascript code base
from Ext Js 4 to Ext JS 5, and I would like to start it doing with the
following approach:
* create a manager5/ directory
* copy incrementally in manager5/ the javascript files forming our
current pvemanagerli
On 13/04/15 18:24, Dietmar Maurer wrote:
Otherwise a change to the parameters from
the GUI can reset the hand-set MTU in /etc/network/interfaces
We never reset parameters like MTU. Do you can a test case?
I can change anything from GUI, without overwriting the MTU settings.
Oops, I was sure t
> In this case we need to known if ceph cluster is running hammer.
> (maybe with rbd cli ?)
>
> or try to enable objectmap, and parse the error and skip it if not supported ?
Oh, I did not thought about that. So I think we should not enable it by default.
Just to keep things easy...
>>So I thing it is good enought to introduce:
>>
>>objectmap: 1|0 ?
yes
>>which defaults to 1
In this case we need to known if ceph cluster is running hammer.
(maybe with rbd cli ?)
or try to enable objectmap, and parse the error and skip it if not supported ?
- Mail original -
De:
14 matches
Mail list logo
