|DACS.VFS(5)||DACS Formats and Conventions||DACS.VFS(5)|
dacs.vfs — the DACS virtual filestore
These files are part of the DACS suite.
The virtual filestore provides flexible ways for DACS and software built on top of DACS to obtain information regardless of how or where the information is stored. The DACS core accesses (almost) all configuration information through the virtual filestore layer, allowing information to be more easily shared and maintained, secured, or organized for better performance.
Sometimes it is easiest to store information in a regular file initially, where it can be modified using an ordinary text editor, but after some growth a database might improve performance. In some situations, accessing the information remotely, via HTTP, makes administration more convenient or is more secure. A goal of the virtual filestore is to make data storage alternatives easier to specify and change.
vfs_uriand Item Types
Many DACS components need to access data
to perform their function.
The documentation for a component will specify a reserved, case-sensitive
name called an item type for each data set
that it may use.
the account information that it manages by the name
Item types start with an alphabetic character followed by zero
or more alphanumerics, hyphens, and underscores.
Item types used by DACS are always completely lower case.
Some other item types used by DACS are
(used by dacskey(1) and others),
(used by dacs.acls(5) and others).
The dacsconf(1) command can list
all reserved item types.
VFS directive is used to
specify the mapping from an item type to a
which describes where and how the information is stored.
Some commands and functions take a
vfs_uri as an argument
to provide a default or override a default.
vfs_uri has the following syntax:
vfs_uri -> [ '['
scheme: [ //
(by default installed as
specifies defaults for many item types.
For example, it defines the "roles file"
For the hypothetical federation domain
by default this would resolve to a file,
That file might consist of entries like:
julia:project1/dacs,admin,horses sara:project2/dacs,project1/dacs,lps sam:project2/dacs,project1/dacs admin:root,project2/admin
The default location of the DACS XML DTDs
dtds) is defined as:
By default, this would resolve to the directory /usr/local/dacs/www/dtd-xsd.
Refer to the VFS directive for additional detail.
Each virtual filestore instance contains either an uninterpreted sequence of bytes (e.g., a Unix file or the output of a program) or an object that contains zero or more items, each of which is associated with a key (i.e., the name of an item relative in its virtual filestore context) and has an uninterpreted sequence of bytes as its value (e.g., a database file, a Unix file containing lines having a particular keyword/value structure, or a directory containing regular files).
For maximum portability, a key should be composed of characters from the Portable Filename Character Set: any alphanumeric character, period, hyphen, or underscore. The true limitation on the character set depends on the underlying storage scheme and URI syntax constraints. There is no a priori limit on naming context or key length.
Distributed Systems Software (www.dss.ca)
Copyright © 2003-2015 Distributed Systems Software.
file that accompanies the distribution
for licensing information.
|DACS Version 1.4.38a||23-Nov-2016||DACS.VFS(5)|
|Table of Contents||
$Id: dacs.vfs.5.xml 2787 2015-03-03 21:26:09Z brachman $