I forgot to mention that volatile disks are created directly on the system
DS. This might not be clear from sunstone.
Were you referring to this when you asked if there is a way to change the
default DS for volatile disks? Or were you thinking about the DS used to
create new Images?
Regards
--
On 08/02/2013 12:54 PM, Carlos Martín Sánchez wrote:
I forgot to mention that volatile disks are created directly on the
system DS. This might not be clear from sunstone.
Were you referring to this when you asked if there is a way to change
the default DS for volatile disks? Or were you
Hi Dmitri,
I confirm Simon's statament that you can't do what you're suggesting due to
OpenNebula's cache mechanism.
However, we have recently found out scalability issues for large
deployments, where the xmlrpc server is a bottleneck. In the next
OpenNebula release we will provide configuration
Hi Jaime,
On Fri, Aug 2, 2013 at 10:26 AM, Jaime Melis jme...@opennebula.org wrote:
However, we have recently found out scalability issues for large
deployments, where the xmlrpc server is a bottleneck. In the next
OpenNebula release we will provide configuration parameters to dramatically
Hi Simon,
yes of course it will be available very soon. We're still working on it but
you can expect that functionality to be there in the next release, or even
the next maintenance release if there is one.
Could you share your scalability experiences with us? Can you a be a bit
more specific?
On Fri, Aug 2, 2013 at 12:21 PM, Jaime Melis jme...@opennebula.org wrote:
Could you share your scalability experiences with us? Can you a be a bit
more specific? What issues have you seen?
I don't have any scalability issues for the moment. My backend / oned
server is dedicate to oned
Hi Simon,
If I understand correctly, by oned won't scale you mean that it's not
currently possible to deploy multiple concurrent oned daemons and *not*
that OpenNebula isn't able to handle very large deployments ( 10.000 vms).
In my reply to Dmitri what I meant is that, once we provide a patch
On Fri, Aug 2, 2013 at 2:21 PM, Jaime Melis jme...@opennebula.org wrote:
If I understand correctly, by oned won't scale you mean that it's not
currently possible to deploy multiple concurrent oned daemons and *not*
that OpenNebula isn't able to handle very large deployments ( 10.000 vms).
Carlos, thank you.
I ran some tests last night - used 'stress' on hosts to generate high CPU and
Memory load. Impressive that ONE almost immediately detects real CPU/MEM usage
on the host and won't deploy any VMs to the host. This is what I was looking
for and it might work...
Thanks.
