Try this thread: https://github.com/apache/cloudstack/issues/3866
On Fri, 24 Apr 2020 at 15:33, Luis Martinez
wrote:
>
> Hi
>
> When installing CS4.13 I get an error that the Database can't be
> updated, reading in google I found that is because is trying to upgrade
> from 4.11 to 4.13, not sure
Hi
When installing CS4.13 I get an error that the Database can't be
updated, reading in google I found that is because is trying to upgrade
from 4.11 to 4.13, not sure why this is happening, is there a way to do
a clean install without upgrade?
Thank you.
I use gluster on ssd r5 (two replicas + arbiter) with ACS for those who
need VM HA. Works fine, but I doubt it will work fine for HDD RAID5, as it
is only for linear workloads without bbu, and other tricks.
пт, 24 апр. 2020 г., 21:15 :
> Hi,
>
> I would not use Gluster in production for VM
Hi,
I would not use Gluster in production for VM workloads, perhaps as
secondary storage where there are mostly sequential writes involved
rather than load of random I/O, it would be fast at that.
CEPH is a much better choice, it's user base is an order of magnitude
larger and so many more
Hello,
I am using gluster 5.11 (3 node replication on raid 5) as a primary storage for
cloudstack 4.11.2 on Centos 7.7, the setup is running stable for more then a
year but performance of VM degraded very much with the increasing number of
active VMs, UI response, boot time of VMs are also
Not necessarily - i.e. you should still observe multiple hundredns of
megabits/sec with default VR offering, with the routing process.
I would pay attention to the network throttling set on XS side, as Vivek
has already suggested in another email.
On Fri, 24 Apr 2020 at 13:51, Olivier GUIN
Hi Andrija,
You wrote that there would be my CPU / RAM ratio which would cause the
throttled on my interface.
What would be the right CPU / RAM ratio?
If you have a recommendation.
I think my problem comes from there ..
I made a VM with 4GB RAM and 4 vCPU at 2Ghz and it works very well!
Hi Olivier,
It may also be a good idea to check your network offerings, perhaps there is an
incorrect limit somewhere that wasn't applied previously and is now limiting
the bandwith.
I remember having such an issue after an upgrade once.
Regards,
Gregor
From:
