Package Name | Comment |
edu.isi.pegasus.planner.client | |
edu.isi.pegasus.planner.ranking | |
org.griphyn.common.catalog | |
org.griphyn.common.catalog.replica | |
org.griphyn.common.catalog.toolkit | |
org.griphyn.common.catalog.transformation | |
org.griphyn.common.catalog.transformation.client | |
org.griphyn.common.catalog.transformation.mapper | |
org.griphyn.common.catalog.work | |
org.griphyn.common.classes | |
org.griphyn.common.util | |
org.griphyn.cPlanner.classes | |
org.griphyn.cPlanner.cluster | |
org.griphyn.cPlanner.cluster.aggregator | |
org.griphyn.cPlanner.code | |
org.griphyn.cPlanner.code.generator | |
org.griphyn.cPlanner.code.generator.condor | |
org.griphyn.cPlanner.code.generator.condor.style | |
org.griphyn.cPlanner.code.gridstart | |
org.griphyn.cPlanner.common | |
org.griphyn.cPlanner.engine | |
org.griphyn.cPlanner.engine.cleanup | |
org.griphyn.cPlanner.namespace | |
org.griphyn.cPlanner.namespace.aggregator | |
org.griphyn.cPlanner.parser | |
org.griphyn.cPlanner.parser.dax | |
org.griphyn.cPlanner.parser.pdax | |
org.griphyn.cPlanner.partitioner | |
org.griphyn.cPlanner.partitioner.graph | |
org.griphyn.cPlanner.poolinfo | |
org.griphyn.cPlanner.provenance.pasoa | |
org.griphyn.cPlanner.provenance.pasoa.pps | |
org.griphyn.cPlanner.provenance.pasoa.producer | |
org.griphyn.cPlanner.selector |
Provides the interface and call-out to the site selector mechanism.
Package Specification
The classes in this package provide a site selection implementation to
select eligible sites from a list of candidates during deferred
planning.
TODO: describe here how it works, e.g. show how the c'tor and
mapJob2ExecPool( SubInfo, List ) work together, what
defaults there are, and link to non-Java call-out for info an using
external applications.
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation,
please see:
@see org.griphyn.cPlanner.common.PegasusProperties
@see org.griphyn.cPlanner.engine.InterPoolEngine
@since 1.2.3
|
org.griphyn.cPlanner.selector.replica | |
org.griphyn.cPlanner.selector.site | |
org.griphyn.cPlanner.selector.site.heft | |
org.griphyn.cPlanner.selector.transformation | |
org.griphyn.cPlanner.toolkit | |
org.griphyn.cPlanner.transfer | |
org.griphyn.cPlanner.transfer.implementation | |
org.griphyn.cPlanner.transfer.refiner | |
org.griphyn.cPlanner.transfer.sls | |
org.griphyn.cPlanner.visualize | |
org.griphyn.cPlanner.visualize.nodeusage | |
org.griphyn.cPlanner.visualize.spaceusage | |
org.griphyn.vdl |
Provides the basic interface that bundles the Chimera classes JAPI.
Package Specification
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation,
please see:
|
org.griphyn.vdl.annotation | |
org.griphyn.vdl.classes |
Bridges between the Virtual Data Language (VDL) and Java data structures.
Package Specification
This set of related classes represents the Virtual Data Language (VDL)
datastructure inside Java classes. The minimum standard interface is
expressed in {@link org.griphyn.vdl.Chimera}, and further refined for
grouping purposes in the {@link org.griphyn.vdl.classes.VDL} parent.
Most of the classes have their counterparts in the XML schema definition
for VDLx, the XML variant of VDL. All classes contain knowledge to
convert their state back into VDLt and VDLx.
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation,
please see:
|
org.griphyn.vdl.dax |
Provides for the classes to interact with the abstract DAG in XML.
Package Specification
The classes in this package provide the JAVA API to construct and
serialize into XML the abstract DAG in XML. To de-serialize from XML
into Java classes, refer to {@link org.griphyn.vdl.parser.DAXParser}.
@see org.griphyn.vdl.classes
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation,
please see:
|
org.griphyn.vdl.dbdriver |
Provides for the database driver encapsulation.
Package Specification
The classes in this package provide an implementation for different
relational database management backend systems. The correct backend
system is dynamically instantiated, steered through properties.
Shown in black are implemented drivers. Red and black show non-working
implementations. In red are shown projected drivers that won't work at
all.
To provide an alternative implementation for an rDBMS, you need to
extend {@link org.griphyn.vdl.dbdriver.DatabaseDriver}.
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation,
please see:
The following properties are understood by most if not all JDBC drivers.
Please note the GVDS-specific prefix. The asterisk should either be used
literally, meaning that the driver configuration applies to all
catalogs, or with the appropriate catalog abbreviation (vdc, ptc,
tc):
vds.db.*.driver
- This property names the class that implements
the {@link org.griphyn.vdl.dbdriver.DatabaseDriver} for a specific
database engine. If the value is a identifier without periods, the prefix
org.griphyn.vdl.dbdrivers. is assumed. Otherwise, the
value denotes the complete Java path to the implementing class. Being
a class name, capitalization is important.
vds.db.*.driver.url
- The URL under which a database may be access. This URL is often
specific to the database itself. However, usually it contains the
host and port (or file) to contact the rDBMS, and the name of the
database within the rDBMS.
vds.db.*.driver.user
- This property specifies the name of the database user as which
to connect to the database.
vds.db.*.driver.password
- The password property specifies the password of the database user.
@see org.griphyn.vdl.dbschema
|
org.griphyn.vdl.dbschema |
Provides the database schema encapsulation.
Package Specification
The classes in this package provide a database independent abstraction
of database access for a variety of catalogs.
To provide an alternative implementation for an existing catalog, you
need to:
- extend the {@link org.griphyn.vdl.dbschema.DatabaseSchema} class.
- implement the appropriate {@link org.griphyn.vdl.dbschema.Catalog}
child interface.
To provide an addition catalog implementation, you need to extend the
{@link org.griphyn.vdl.dbschema.Catalog} interface. In the next step,
you will need to provide an implementation as before.
Currently, several concrete catalogs are implemented in Chimera:
- The Provenance Tracking Catalog {@link org.griphyn.vdl.dbschema.PTC}
- The Virtual Data Catalog {@link org.griphyn.vdl.dbschema.VDC}
- An extension of the VDC {@link org.griphyn.vdl.dbschema.Advanced}
- Joining attributes to Virtual Data objects {@link org.griphyn.vdl.dbschema.Annotation}
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation,
please see:
@see org.griphyn.vdl.dbdriver
@see org.griphyn.vdl.annotation
|
org.griphyn.vdl.diagnozer | |
org.griphyn.vdl.directive |
Provides the API to the abstract planner for portals, CLI tools, etc.
Package Specification
The classes in this package provide an implementation which bridges
between the intricate, and at times difficult to use, abstract planner
classes, and code that is using the abstract planner. The latter
includes things like portals, de-agonizers and command-line tools.
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation,
please see:
@since GVDS 1.2.1
|
org.griphyn.vdl.euryale |
Provides the Euryale prototypical replanning-capable planner.
Package Specification
The classes in this package provide a lean implementation which bridges
from the abstract DAG in XML (DAX) format to Condor DAGMan specific
output files, which relies on Euryale's replanning features.
Related Documentation
For overviews, tutorials, examples, guides, and tool documentation,
please see:
@since GVDS 1.2.1
|
org.griphyn.vdl.invocation | |
org.griphyn.vdl.parser | |
org.griphyn.vdl.planner | |
org.griphyn.vdl.router | |
org.griphyn.vdl.toolkit | |
org.griphyn.vdl.util | |
org.griphyn.vdl.workflow | |