Action Testbed Fedora

Assigned

ABR + JRG

Prev assigned

Tasks adressed

TaskA.3

Time estimated

2md

Time used

6h

Priority

2

Status

Finished

Iteration

11

Notes

We must provide a convinient way to setup the Fedora part of the DOMS testbed. This should optimally be a install script for Fedora 3.0.

The testbed need not focus on speed or efficiency, but on providing a production like interface. For this purpose, these design choices have been made. They are of course subject to modification by the people working on this action.

• We will use the fedora included Mckoi database, rather than a seperate mysql database.

• We will use the tomcat-users.xml file for tomcat user management
• We will use the Fedora users.xml file for fedora user management
• We will not use journaling
• Fedora has been officially upgraded to work with Java 1.6, so all parts of the testbed will use that version
• There will be no xacml policies at first
• We will use the included relation triplestore, as this functionality is paramount.

The testbed will not run in the tomcat shipped with Fedora. The main script of Action Testbed Delivery will set up the tomcat that the scripts of all the other webservice testbed actions will use.

Report

Fedora 3.0 has been bundled in the testbed. It is configured to run on a tomcat running on port 8080. To change that, you must edit the config files. It uses mckoi database, which it accesses by a relative path from the tomcat installation. As so, it must always be installed alongside it's tomcat. The tomcat enviroment variables automatically sets this location as the fedora_home. It uses the builtin triplestore. There is no ssl or xacml or journaling.

Fedora is normally installed by an interactive installer, which can take a configuration file insted. There are about a 1000 different places, where the properties are coded into the final install. Bundling a final install turned out to be a bad idea. A future version should work directly with the fedora installer.

Checklist For Working On An Action

The Life Cycle of an Action:

• Assign people for action definition: Done at start of iteration status meeting. Fill out Assigned

• Define the action: Describe information about what is to be done and how. Fill out Tasks Addressed and Time Estimated.

• Review the definition: Get another project group member to review the action definition, and update it.

• Assign people for action implementation: Done by project manager, usually the same persons who wrote the definition. Fill out Assigned and Prev assigned if new persons are assigned.

• Implement the action: See details below

• Review the action: Get another project group member to review what is implemented (code and documentation), and update it.

• Finish the action: Change the status to "Finished" and update the "time used" field on the action page.

Please make sure that you address the below issues, when working on an action:

• Update the state of the action to "In Progress" when you start working on it.
• Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.

• Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. Hint: Continually updating the "Time used" field will make it easier for you.

• Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.