Hi all,
In OpenNebula, it seems we can easily set it up to use Ceph as a
datastore for images, cloning non-persistent images to make temporary
copies, etc.
We can also have the images stored as files on the frontend computer and
dolled out via SSH; and in the case of persistent images, copied
Dear OpenNebula users,
I need some information about the ONE database management / maintenance, on
which basis are old values removed to keep the DB small? Is it based on time
intervals, DB size or something different? And furthermore, can it be
configured?
I looked through the net and
Hello i had some hardware failure .. but i had some backup made .. so
after installed full system back .. i had to recopy database from old
backup .. and files .. added manualy in database the images .. to match
the old configs and info .. but now if try to clone any image .. i get
duplicate
Indices are controlled by OpenNebula and the last id is saved to table
pool_control. Modify it so the ID is greater that the latest image
and start oned again.
On Thu, Mar 13, 2014 at 2:34 PM, Ionut Popovici io...@hackaserver.com wrote:
Hello i had some hardware failure .. but i had some backup
Hi,
On Thu, Mar 13, 2014 at 2:34 PM, Ionut Popovici io...@hackaserver.com
wrote:
Hello i had some hardware failure .. but i had some backup made .. so
after installed full system back .. i had to recopy database from old
backup .. and files .. added manualy in database the images .. to match
* VMs are never deleted just marked as DONE. This data will be used
later for accounting.
* The amount of monitoring data can be configured in oned.conf. Check
INTERVAL and EXPIRATION parameters [1].
* Other objects are deleted as soon as you issue a delete action.
[1]
Hi,
On Thu, Mar 13, 2014 at 4:25 PM, Javier Fontan jfon...@opennebula.orgwrote:
* VMs are never deleted just marked as DONE. This data will be used
later for accounting.
* The amount of monitoring data can be configured in oned.conf. Check
INTERVAL and EXPIRATION parameters [1].
* Other
