> > The plan is to release 3.2 with ceph firefly packages. You would you lose
> support then (why)?
>
> No not as long as ceph tells me to upgrade ;-) But most probably that won't
> happen before Firefly minor version 3 or 4.
The plan for 3.2 is to wait for Firefly, so I guess we can go that way.
> > The disk window is simply too overloaded with all that IO throttle
> > paramaters.
> > They are totally pointless for 95% of our users.
>
> yes all but why not keeping the 4 simple values like before
it is already grown to 8 values (too much).
> and just have all settings in the seperate w
Am 25.01.2014 10:32, schrieb Dietmar Maurer:
yes that's correct but i loose any support while doing so ;-)
I do not understand that. You use pvetest with your production environment?
Sorry no i just thought about the future sometime these will move to default pve
repo.
The plan is to releas
Am 25.01.2014 10:14, schrieb Dietmar Maurer:
i would like to vote for bringing back the disk throttle parameters to the
creation
The disk window is simply too overloaded with all that IO throttle paramaters.
They are totally pointless for 95% of our users.
yes all but why not keeping the
> >> yes that's correct but i loose any support while doing so ;-)
> >
> > I do not understand that. You use pvetest with your production environment?
>
> Sorry no i just thought about the future sometime these will move to default
> pve
> repo.
The plan is to release 3.2 with ceph firefly packa
Am 25.01.2014 um 10:13 schrieb Dietmar Maurer :
>> yes that's correct but i loose any support while doing so ;-)
>
> I do not understand that. You use pvetest with your production environment?
Sorry no i just thought about the future sometime these will move to default
pve repo.
>
__
> > wizard or having a central place to setup defaults.
>
> That would work, but currently there is no central place to setup defaults.
Maybe an additional attribute on the storage definition?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http:/
> i would like to vote for bringing back the disk throttle parameters to the
> creation
The disk window is simply too overloaded with all that IO throttle paramaters.
They are totally pointless for 95% of our users.
> wizard or having a central place to setup defaults.
That would work, but cur
> yes that's correct but i loose any support while doing so ;-)
I do not understand that. You use pvetest with your production environment?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Am 25.01.2014 10:03, schrieb Dietmar Maurer:
Personally i would also prefer if the ceph packages would be in a seperate repo
-
so i don't risk an unwated update of my ceph servers while using the pve repo.
We need the ceph client packages, so I need to include them.
AFAIR we discussed ceph pa
Hello,
i would like to vote for bringing back the disk throttle parameters to
the creation wizard or having a central place to setup defaults.
Without it it can happen very easily that you forgot to limit a disk and
then overload your storage.
Greets,
Stefan
> Personally i would also prefer if the ceph packages would be in a seperate
> repo -
> so i don't risk an unwated update of my ceph servers while using the pve repo.
We need the ceph client packages, so I need to include them.
AFAIR we discussed ceph package versions already on this list, and t
Am 25.01.2014 08:15, schrieb Dietmar Maurer:
So is it just a dependency or does it really compare on changes from dumpling to
emperor?
It should work with dumpling, so I can change that dependency if you need it?
would be nice.
Personally i would also prefer if the ceph packages would be in
13 matches
Mail list logo
