Version 4 (modified by aydan, 10 years ago)

--

Orca TODO List

  • Change the build to use a maven repository at RENCI
  • Move the continuous build system from DUKE to RENCI
  • Move the orca web site to RENCI
  • Reorganize the continuous build system to have multiple sub-projects
  • Improve and update the documentation

** First step: describe how to set the dev environment

  • Simplify installation. Can we have a wizzard?
  • Add unit tests at every possible level
  • Add functional tests at every possible level
  • Determine the license and text to use as header in source files. The current text is Duke-specific. The license is Eclipse. I would like to keep Eclipse as the license.
  • Run with real resources

Code-level items

* Add support for Amazon and Eucalyptus * Make cross-actor calls asynchronous (should not hold the master lock) * Move database and guid configuration from the xml file to the container.properties. Move the globals section from config.xml to container.properties * Move the image library into cod * Cleanup cod: there is some dead/must be better code * Index actors using guid instead of actor name (avoid name collisions) * Change management API to use actor guid instead of actor name * Audit the management API and check how we handle authentication and authorization * Review the management API and determine what needs to be pulled down to the core and what should stay in the standard management package * Decide if there are missing management API and add them * Audit all security checks