Wednesday, July 23, 2008

Now that a web client accessing Ogsa-Dai is working, now what?

Today I spent a lot of time re-firing-up the development machine and slightly expanding my test to make sure that thethe time series was working in addition to the spatial series. Yesterday, Air Conditioner installation ousted me from the lab for a good portion of the day, so I was planning what I would do once things got running and running them by Jeremy, I am going ahead and posting a copy of that list here:

  1. Shorter Term, Higher priority:
    1. Expansion of the RODSAdai and RODSAdai-web projects so that instead of just an index and a page that loads a fixed spatial series… you get some pages that let you try different queries, different data-resources (selectable from a list generated from the properties file), and an admin screen for adding, removing, and modifying properties. (shorter term, higher priority)
    2. (anticipating) Work with Jeremy to set up finals of RODSAdai environment, in the meantime set up different RODS environments (3 computers, each with a subset of data) in the CDC lab that can connect to each other across the local globus network.
    3. Look into creating a local, database based security manager that uses encrypted user information within a database instead of a “logins.txt” file for OGSA-DAI database authentication/authorization.
  2. Shorter term, Lower Priority:
    1. Brush up documentation of RODS/Adai.
    2. Outline and fill as best possible, the “Should Peter walk into the path of a greyhound dream liner” document.
    3. See if insecure tomcat’s OGSA-DAI project can be moved into JBoss, if not, find a way for coexistence, or plan out having one insecure tomcat OGSA-DAI instance somewhere accessible for build stations.
  3. Longer term, Higher Priority:
    1. (anticipating) Discuss and document finer layers of authorization in addition to the authentication and encryption afforded by Globus and OGSA-DAI
    2. Work on a security management subsystem that allows one to check the validity of a proxy certificate and/or create them as needed, and find ways to work that into the rods portal. The idea being that if the User authenticates, a proxy certificate should be issued for however long they are logged in. This may mean user-specific proxy certificates and integration of things like PURSe and MyProxy.
  4. Longer term, Lower Priority:
    1. Continue researching security policies for Tomcat.

Many of these things are subject to change, but that is where I am right now, I also have a particular interest in integrating RODS and RODSAdai for the conference. I feel like the end goal is to have RODS with two different data sets on two machines and both have the ability to see the others data.

No comments: