Feature #508
Either let the oned.db position configurabe o move vm staging somewhere else (i.e. /var/lib/images)
Status: | Closed | Start date: | 03/02/2011 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Core & System | |||
Target version: | Release 3.4 - Beta | |||
Resolution: | fixed | Pull request: |
Description
Either solution could help to have the db on the front end internal disk when using nfs.
Associated revisions
History
#1 Updated by Javi Fontan over 10 years ago
- Target version deleted (
Release 2.2)
This change wont make version 2.2 as it is already in feature freeze. Meanwhile (and for production installations) mysql database is encouraged, it has better performance and also does not have this problem.
sqlite to mysql migration can be easily done making a dump of the database without table creation and using that to populate the database OpenNebula creates in mysql in the first start.
#2 Updated by Ruben S. Montero over 9 years ago
- Target version set to Release 3.4 - Beta
#3 Updated by Ruben S. Montero over 9 years ago
- Status changed from New to Closed
- Resolution set to fixed
The new datastore system, includes an special system datastore for running VMs.