Kepler

FirstStakeholdersMeeting

2008-05-12T05:56:16Z

uid=mcphillips,o=unaffiliated changed this page on Sun May 11 22:56:16 PDT 2008:

Line 187 was replaced by line 187

- * __Parking.__ The recommended parking lot is Visitor Parking 47 (see [campus map|http://visit.ucdavis.edu/map/map_detail.cfm?centerTile=8_9#map]). Parking permits cost $6.00 per day. Permit dispensers accept quarters, one-dollar bills, five-dollar bills or VISA and MasterCard.

+ * __Parking.__ The recommended parking lot is Visitor Parking 47 (see [interactive campus map|http://visit.ucdavis.edu/map/map_detail.cfm?centerTile=8_9#map]). Parking permits cost $6.00 per day. Permit dispensers accept quarters, one-dollar bills, five-dollar bills or VISA and MasterCard.

Line 189 was replaced by line 189

- * __Directions.__ [Driving from Hallmark Inn to Kemper Hall|http://maps.google.com/maps?f=d&hl=en&geocode=16651695792211157440,38.536025,-121.755429&saddr=110+F+St,+Davis,+CA+95616&daddr=38.536417,-121.754415&mra=dme&mrcr=0&mrsp=1&sz=16&sll=38.537105,-121.747892&sspn=0.013478,0.018346&ie=UTF8&ll=38.537844,-121.747699&spn=0.013478,0.018346&z=16] . (Note that walkers can take a more direct route. It is a nice 20 minute walk or so.)

+ * __Directions.__ [Driving from Hallmark Inn to Kemper Hall|http://maps.google.com/maps?f=d&hl=en&geocode=16651695792211157440,38.536025,-121.755429&saddr=110+F+St,+Davis,+CA+95616&daddr=38.536417,-121.754415&mra=dme&mrcr=0&mrsp=1&sz=16&sll=38.537105,-121.747892&sspn=0.013478,0.018346&ie=UTF8&ll=38.537844,-121.747699&spn=0.013478,0.018346&z=16] . (Note that walkers can take a more direct route. It is a nice 25 minute walk or so. Download [complete campus map|http://www.ormp.ucdavis.edu/environreview/onlinedocs/campusmap_front.pdf].)

KeplerProject

2008-05-09T20:38:52Z

uid=jones,o=NCEAS changed this page on Fri May 09 13:38:52 PDT 2008:

Line 6 was replaced by line 6

- May 9, 2008|The [Hydrant|http://www.hpc.jcu.edu.au/hydrant/] web-based workflow execution system released

+ |May 9, 2008|The [Hydrant|http://www.hpc.jcu.edu.au/hydrant/] web-based workflow execution system released

KeplerSRB

2008-05-06T22:13:43Z

uid=aschultz,o=NCEAS changed this page on Tue May 06 15:13:43 PDT 2008:

Line 2 was replaced by line 2

- Kepler recently provides support for the Storage Resource Broker (SRB) storage management system as an interface to provide efficient storage functionality. SRB serves as a storage management system in the Grid environment. SRB provides secure and optimized file transfer functions along with seamlessly access to data from heterogeneous physical resource using a logical namespace. Moreover, SRB includes built-in replication, bulk-replication, and a metadata query functionality through a MetaData Catalog (MCAT).

+ Kepler recently provides support for the Storage Resource Broker (SRB) storage management system as an interface to provide efficient storage functionality. SRB serves as a storage management system in the Grid environment. SRB provides secure and optimized file transfer functions along with seamless access to data from heterogeneous physical resource using a logical namespace. Moreover, SRB includes built-in replication, bulk-replication, and a metadata query functionality through a MetaData Catalog (MCAT).

Line 5 was replaced by line 5

- Using SRB in Kepler provides an efficient storage management; data access and transfer functionality, server side processing of data using sproxy commands and and efficient search functionality using metadata. Moreover, as Kepler is a cross-project collaboration extending to various scientific disciplines, SRB provides data access to diverse repositories using a single namespace.

+ Using SRB in Kepler provides an efficient storage management; data access and transfer functionality, server side processing of data using sproxy commands and efficient search functionality using metadata. Moreover, as Kepler is a cross-project collaboration extending to various scientific disciplines, SRB provides data access to diverse repositories using a single namespace.

KSWEncapsulationSpecification

2008-05-06T22:11:53Z

uid=aschultz,o=NCEAS changed this page on Tue May 06 15:11:53 PDT 2008:

 Line 46 was replaced by line 46
-- After much discussion, it was decided that the definition of actor within this system was somewhat abiguous.  Here, I try to clarify the definitions of several terms and try to describe how these interrelated systems will work.
++ After much discussion, it was decided that the definition of actor within this system was somewhat ambiguous.  Here, I try to clarify the definitions of several terms and try to describe how these interrelated systems will work.
 Line 61 was replaced by line 61
-- In any case, the moml parser will need to be modified to handle id references instead of hard coded class names.  The parser will need to identify that a reference to an lsid has been made, then call the OM to locate the object with that id and intantiate it (this may be a java class or it might just be another metadata file).
++ In any case, the moml parser will need to be modified to handle id references instead of hard coded class names.  The parser will need to identify that a reference to an lsid has been made, then call the OM to locate the object with that id and instantiate it (this may be a java class or it might just be another metadata file).
 Line 69 was replaced by line 69
-- With a model such as this, where we have a metadata document describing some other object (maybe a binary one), we will need a server that is capable of capturing, serving and searching metadata while linking multiple metadata files to one non-metadat object.  It occurs to me that Metacat would work perfectly for this purpose.  The actors and workflows are now just xml metadata docs that need to link to a java class.  Metacat can store the actors and even provide the link to the binary class file.  It could also store binary shared object (dll) libraries which will be linked to through the actor's dependency information.
++ With a model such as this, where we have a metadata document describing some other object (maybe a binary one), we will need a server that is capable of capturing, serving and searching metadata while linking multiple metadata files to one non-metadata object.  It occurs to me that Metacat would work perfectly for this purpose.  The actors and workflows are now just xml metadata docs that need to link to a java class.  Metacat can store the actors and even provide the link to the binary class file.  It could also store binary shared object (dll) libraries which will be linked to through the actor's dependency information.

KeplerObjectManager

2008-05-06T22:07:13Z

uid=aschultz,o=NCEAS changed this page on Tue May 06 15:07:13 PDT 2008:

Line 114 was replaced by line 114

- This type of Kar file is the basis of the binary extension and distribution mechanism. These Kar files are intended to satify the Kar Functional Requirement 3 above. They are collections of components developed by a single individual/organization which consists of java classes, java jars, native binaries, native libraries, etc. This is the only type of kar file which can contain these types of components. The package will always be distributed in its entirity and the developing organization is responsible for the individual components to be able to function together while using the same supporting classes.

+ This type of Kar file is the basis of the binary extension and distribution mechanism. These Kar files are intended to satisfy the Kar Functional Requirement 3 above. They are collections of components developed by a single individual/organization which consists of java classes, java jars, native binaries, native libraries, etc. This is the only type of kar file which can contain these types of components. The package will always be distributed in its entirity and the developing organization is responsible for the individual components to be able to function together while using the same supporting classes.

DevelopmentForKepler

2008-05-06T21:57:38Z

uid=aschultz,o=NCEAS changed this page on Tue May 06 14:57:38 PDT 2008:

 Line 17 was replaced by line 17
-- We only support access to CVS using an SSH login. Please see the [CVS Faq|] for details on how to configure CVS access using SSH.
++ We only support access to CVS using an SSH login. Please see the [CVS Faq|http://cvs.ecoinformatics.org/HOWTO-cvs-over-ssh.html] for details on how to configure CVS access using SSH.
 Line 20 was replaced by line 20
-- Anonymous read-only CVS access is available by configuring your CVS to connect over SSH with the username __'anonymous'__ and use __'guestaccess'__ for the password.
++ Anonymous read-only CVS access is available by configuring your CVS to connect over SSH with the username __'anonymous'__ and password __'guestaccess'__.
 Line 23 was replaced by line 23
-- Named accounts start off initially as read-only, but can be upgraded to read-write as described in the Management|KeplerManagement] section. Named accounts are available by writing a brief email request as described on the [Getting Involved|GettingInvolved] page.
++ Named accounts start off initially as read-only, but can be upgraded to read-write as described in the [Management|KeplerManagement] section. Named accounts are available by writing a brief email request as described on the [Getting Involved|GettingInvolved] page.
 Line 45 was replaced by line 45
-- The Eclipse can be used as a development environment for Kepler. The information on downloading, installing and configuring Eclipse, connecting to the Kepler CVS repository, downloading the source and building it can be found at the [Kepler Eclipse webpage|UsingEclipseForKeplerDevelopment].
++ Eclipse can be used as a development environment for Kepler. The information on downloading, installing and configuring Eclipse, connecting to the Kepler CVS repository, downloading the source and building it can be found at the [Kepler Eclipse webpage|UsingEclipseForKeplerDevelopment].

GettingInvolved

2008-05-06T21:49:24Z

uid=aschultz,o=NCEAS changed this page on Tue May 06 14:49:24 PDT 2008:

Line 7 was replaced by line 7

- ** If you have questions or comments related to the using Kepler, you can subscribe to the [kepler-users mailing list|http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users] (see [Archives|http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/kepler-users/]). This list is intended mainly as a support channel (see below if you'd like to make contributions or discuss Kepler development).

+ ** If you have questions or comments related to using Kepler, you can subscribe to the [kepler-users mailing list|http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users] (see [Archives|http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/kepler-users/]). This list is intended mainly as a support channel (see below if you'd like to make contributions or discuss Kepler development).

WorkingDistributedFeatures

2008-04-25T20:30:43Z

uid=dsledge,o=LTER changed this page on Fri Apr 25 13:30:43 PDT 2008:

Line 7 was replaced by line 7

- Building a distributed workflow in Kepler is done much like building a regular workflow. The main difference is that any part of the workflow that you would like to be distributed over multiple CPUs must be created inside a DistributedCompositeActor (DCA). You can find the DCA by searching for it in the actor library. Drag a DCA out onto the canvas, then right click on it and choose "Open Actor" to add components. Examples can be found in the kepler/lib/workflow/distributed directory. At this time, only SDF directors have been tested within a DCA. At this time the DCA must contain an SDF director.

+ Building a distributed workflow in Kepler is done much like building a regular workflow. The main difference is that any part of the workflow that you would like to be distributed over multiple CPUs must be created inside a DistributedCompositeActor (DCA). You can find the DCA by searching for it in the actor library. Drag a DCA out onto the canvas, then right click on it and choose "Open Actor" to add components. Examples can be found in the kepler/workflows/distributed directory. At this time, only SDF directors have been tested within a DCA. At this time the DCA must contain an SDF director.

Documentation

2008-04-25T16:51:24Z

uid=kanderson,o=unaffiliated changed this page on Fri Apr 25 09:51:24 PDT 2008:

 Lines 1-3 were replaced by lines 1-4
-- !Kepler Getting Started Guide
-- *[Latest PDF version|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/kepler-docs/user/draft-getting-started-guide.pdf]
-- *[Latest MSOffice Word version|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/kepler-docs/user/draft-getting-started-guide.doc]
++ !Kepler Getting Started Guide:
++ *[Latest PDF version|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/kepler-docs/user/app/getting-started-guide.pdf]
++ *[Latest MSOffice Word version|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/kepler-docs/user/getting-started-guide.doc]
++
 Lines 5-6 were replaced by lines 6-7
-- *[Latest PDF version:|]
-- *[Latest MSOffice Word Version|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/kepler-docs/user/Actor_Docs_for_Users_In_Progress.doc]
++ *[Latest PDF version:|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/kepler-docs/user/app/ActorReference.pdf]
++
 Lines 8-10 were replaced by line 9
-- *[Latest PDF version:|]
-- *[Latest MSOffice Word Version|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/kepler-docs/user/User_Manual_Draft_Outline.doc]
-- *[Kepler User Manual (wiki page, in progress)|UserManualIndex]
++ *[Latest PDF version:|http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/kepler-docs/user/app/UserManual.pdf]
 Lines 17-18 were replaced by line 16
-- !Kepler Glossary
-- *[A Glossary of Kepler Terms (in progress)|Kepler_Glossary]
++

InstallingDistributedWorkflows

2008-04-24T18:54:51Z

uid=dsledge,o=LTER changed this page on Thu Apr 24 11:54:51 PDT 2008:

Line 15 was replaced by line 15

- start rmiregistry -J-classpath -J%KEPLER%/build/classes;%PTII%/build/classes;%KEPLER%/lib/jar/jargon_v2.0.jar

+ start "rmiregistry -J-classpath '-J%KEPLER%/build/classes;%PTII%/build/classes;%KEPLER%/lib/jar/jargon_v2.0.jar'"

Line 35 was replaced by line 35

- For your first workflow, try using one of the examples in lib/workflow/distributed. There are several in there that are known to work and should get you started.

+ For your first workflow, try using one of the examples in workflows/distributed. There are several in there that are known to work and should get you started.

RevisingTheBuildSystem

2008-04-19T01:16:14Z

uid=mcphillips,o=unaffiliated changed this page on Fri Apr 18 18:16:14 PDT 2008:

Line 1 was replaced by line 1

- !! Background

+ !!! Background

ProposedBuildSystemUseCases

2008-04-19T00:55:49Z

uid=mcphillips,o=unaffiliated changed this page on Fri Apr 18 17:55:49 PDT 2008:

Lines 40-41 were replaced by lines 40-41

- * Automatically edit a set source files to remove unneeded imports and expand package imports to specific class imports.

- * Automatically edit and move source files as needed to rename or move classes and packages.

+ * Edit a set source files to remove unneeded imports and expand package imports to specific class imports.

+ * Edit and move source files as needed to rename or move classes and packages.

CurrentBuildSystemUseCases

2008-04-19T00:20:21Z

uid=mcphillips,o=unaffiliated changed this page on Fri Apr 18 17:20:21 PDT 2008:

Line 3 was replaced by line 3

- Safely [revising the build system|RevisingTheBuildSystem] requires understanding the functions of the current system. The purpose of of this page is not to capture every detail about how the current system works, but rather to model the key functions (at the level of what are sometimes called 'business' use cases) so that the functions needed in the future can be maintained, and so that the current functions can be compared with those [functions proposed|ProposedBuildSystemUseCases] for the revised build system.

+ Safely [revising the build system|RevisingTheBuildSystem] as part of the [Kepler/CORE|KeplerCORE] effort requires understanding the functions of the current system. The purpose of this document is not to capture every detail about how the current system works, but rather to model the key functions (at the level of what are sometimes called 'business' use cases) so that (a) the functions needed in the future can be maintained, and (b) the current functions can be compared with those [functions proposed|ProposedBuildSystemUseCases] for the revised build system.

Line 5 was replaced by line 5

- The following captures what the current build system does from the point of view of a Kepler developer using the build system. Note that we treat the variously optimized implementations of particular tasks as the same business use case.

+ The following captures what the current build system does from the point of view of a Kepler developer. Note that we treat the variously optimized implementations of particular tasks as the same business use case.

HotTopics

2008-04-18T22:46:03Z

uid=mcphillips,o=unaffiliated changed this page on Fri Apr 18 15:46:03 PDT 2008:

Line 21 was replaced by line 21

- * [Build system support for Kepler/CORE and extensions|BuildSystem]

+ * [Revising the build system to support extensions|RevisingTheBuildSystem]

BuildSystem

2008-04-18T18:53:08Z

uid=mcphillips,o=unaffiliated changed this page on Fri Apr 18 11:53:08 PDT 2008:

Line 9 was replaced by line 9

- [Current build system use cases|CurrentBuildSystemUseCases]

+ [Current build system use cases|CurrentBuildSystemUseCases].

Line 13 was replaced by line 13

- [Diagrams depicting compile-time dependencies on 3rd-party libraries|JarDependencies.pdf] This file can be searched by jar name, Java class, or package name to reveal dependencies on 3rd-party jar files apparent at compile time (i.e., in the source code). The oval in the center of each diagram represents the jar. Boxes to the right of the of the jar are Kepler packages and classes that use the jar, and boxes to the left are packages and classes in the jar used by these Kepler components.

+ [Diagrams depicting compile-time dependencies on 3rd-party libraries|JarDependencies.pdf]. This file can be searched by jar name, Java class, or package name to reveal dependencies on 3rd-party jar files apparent at compile time (i.e., in the source code). The oval in the center of each diagram represents the jar. Boxes to the right of the of the jar are Kepler packages and classes that use the jar, and boxes to the left are packages and classes in the jar used by these Kepler components.