Configurable location for $ONE_LOCATION/var/one.db
|Category:||Core & System|
|Target version:||Release 3.4|
|Affected Versions:||OpenNebula 3.0|
this affects both 2.2 and 3.0, and I'd even suggest a "high" priority.
Robert's workaround is a lot of hassle !
On Wed, 2011-10-26 at 10:20 -0400, Robert Parrott wrote:
We got stung with this issue as well. Our short term approach was to
create an iscsi mount (i.e. block storage) and put everything in var/
there, and migrate to MySQL when we have a window of downtime.
As far as I can tell there's no way in ONE to specify that the DB
location should be separate from the other contents of /var/lib/one or
$ONE_LOCATION/var, which is why we used a different protocol. I
consider this a defect, though I haven't filed a ticket on it.
On Wed, Oct 26, 2011 at 10:01 AM, Steffen Neumann <firstname.lastname@example.org> wrote:
I have to move one.db (which is currently living on an NFS volume,
which is dangerous according to the docs1) to a local filesystem
on the head node.
Where do I specify the path to one.db ? The documentation 
does not mention further arguments in oned.conf DB section
DB = [ backend = "sqlite" ].
The only reference to a variable DB location I found was
DB: sqlite:///var/one/oneacct.db in $ONE_LOCATION/etc/acctd.conf
but nothing for one.db.
Do I need to hack the source or switch to MySQL ?
Serving $ONE_LOCATION from a central storage/NAS might be a common
scenario, so this could be a fairly important issue.
#2 Updated by Ruben S. Montero about 9 years ago
- Status changed from New to Closed
- Target version set to Release 3.4
- Resolution set to worksforme
Since OpenNebula 3.4 the images directory are in a special datastore, so there is no longer the requirement to export the whole /var/lib/one directory. The location of one.db is not configurable but now there are no problems with NFS shares. You can link the file to any other location of the FS hierarchy.
I am closing this. We'll reopen if the current situation is not satisfactory.