Bug #490
milestones to release greyhole
100%
Description
warnings on certain mount pointsnot show mount points that are full (like my two or three iso-mounted images)sqliteshow in the storage pool page the mounts that are in the db and not mounted atm, to allow the user to remove them if it's gone for goodstart a server by default with the default serverschange greyhole to produce a PID in the .pid file
- allow the user to add mount points (this supports remote mounted file systems, in absence of automatic detection)
History
#1 Updated by cpg about 12 years ago
for the sql integration, it appears that only the following functions are mysql specific:
mysql_connect($db_host, $db_user, $db_pass) mysql_select_db($db_name); mysql_query(); mysql_escape_string($filename) mysql_fetch_object($result) mysql_num_rows($result) mysql_free_result($result);
there may be some mysql-specific sql too :(
there are two possible candidates for a shim layer to cover both mysql and sqlite:
- php-pdo (164k, but has a lot of dependencies)
- php-pear-MDB2 (724k, and somehow it's installed already in my hda and has some examples in it)
#2 Updated by gboudreau about 12 years ago
MDB2: Latest stable: 2007-05-03 (3 years old), Latest beta: 2009-01-14 (more than a year ago)
That seems quite old.
If you really want to use a data-access abstraction layer, I suggest PDO.
Myself, I'd use a home-made library; just abstract each db function in a new function, with a simple switch on the selected DBMS. Anything else would only add unnecessary layers & complexity for the simple use I do of the database.
#3 Updated by cpg about 12 years ago
- Assignee set to cpg
looks like there was almost a one-to-one mapping to the sqlite calls. i put a version zero of greyhole with sqlite support in the shared dropbox folder. by default, it should behave identically as the latest (i.e. using mysql).
to turn on sqlite, set sqlite = TRUE in the greyhole.conf file.
the file is called
greyhole-v0.sqlite
guillaume, if you have a moment, would you take a gander?
#4 Updated by Anonymous about 12 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Applied in changeset commit:"3701e5f227ec3cd26a2ca8b72ff94e1c8f47c6fa".
#5 Updated by cpg about 12 years ago
- Status changed from Closed to Assigned
- % Done changed from 100 to 70
#6 Updated by cpg almost 12 years ago
NOTE: See this thread this thread for discussions of possible solutions for issue number 5 above.
#7 Updated by cpg almost 12 years ago
item number 5 is fixed in git top of tree. the user is shown partitions in the pool with a warning sign, and only the ability to remove them.
#8 Updated by cpg almost 12 years ago
issue number 2 was done already. anything below 200mb is not shown
#9 Updated by cpg over 11 years ago
- Status changed from Assigned to Closed
#10 Updated by cpg over 11 years ago
- % Done changed from 70 to 100
we already put the warnings on root mounts
Also available in: Atom