Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

GOCDB/Release4/Development/Recently Completed

From EGIWiki
Jump to navigation Jump to search

Recent Completed Developments

  • GOCDB-4.2 Released - 25 November 2011
    • Scoping of sites and service endpoints Sites and SEs marked as being part of the EGI grid will be exposed to the central operational tools while Local entities are not considered part of the EGI infrastructure.
  • GOCDB-4.1 Release - 01 November 2011
    • Refactored PROM db API. The underlying database code has been refactored considerably for greater flexibility and stability. All changes to the database are now atomic facilitating transaction demarcation in higher level business routines. Database interactions are now performed through a database agnostic API interface.
      • (Before v4.1, the GOCDB PROM API did not allow transaction demarcation in high level business operations, such as inserting a site and adding new SE because explicit commits and rollbacks were declared in low-level PLSQL functions including fnNewLink(), fnUpdateObject(), fnDeleteObject(), fnDeleteLink(). Consequently, any business operation that invoked these functions multiple times in a single processing unit was not atomic, and gocdb 4.0 could leave the db in an inconsistent state if an error occurred since full rollback was not possible (e.g. on site creation Savannah 74860). This almost certainly accounted for a number of previously reported data inconsistencies. Refactoring the database logic was therefore high priority and is a regionalisation pre-requisite; either all or none of the data should be committed to the central gocdb when publishing from regional to central).
    • Refactored much of the code base initially (inc. MVC) to support scoping but also to provide more flexibility long term (using a flexible controller per page architecture with view templates). This will make future change requests easier to fulfill and gives us more flexibility to make user interface improvements.
      • (Before v4.1, GOCDB used a generic module for drawing all forms and GUI components such as tables. This module defined a single code path which was too rigid, making it difficult to deal with form/table requirements on a per-page basis).
    • New View Site page (to support scoping and to address user issues with the current View Site page)
    • New View Service Endpoint page
    • Added current UTC time to New Downtime page
    • Added context sensitive page titles
    • Added "All" button to table view
  • Refactored database code to be atomic (required to implement scoping) - Oct 2011 (release into production end Oct/start-Nov) (details below)
  • New Downtime interface much improved, moved to single page + can now select all endpoints under one site - September 2011
  • Moved Site, User and Endpoint manipulation to new MVC architecture ready to support scoping - July 2011
  • Fixed a few long term bugs with adding and editing sites and users - July 2011
  • Increased front end responsiveness - July 2011
  • Cleaned old roles - June 2011
  • Added a URL field to service endpoint objects to support UNICORE services - May 2011 (note, even though a single URL field is displayed per Endpoint, a new Gocdb_Endpoint_Location entity was created in order to link multiple service endpoint locations per SE if this becomes a future requirement - see Media:GocdbGlue2UnicoreV2.pdf).
  • Add a "my site" link in the main menu - May 2011 (note, this uses the new controller-per page with templates design as summarized below).
  • Record Certification Status History - 10th March 2011
  • Allow authorised operators to suspend sites at central level - March 2011
  • Show when a site entered the current production status - March 2011
  • Consolidated Wiki and all documentation.