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 @ egi.eu.

Difference between revisions of "GOCDB/Release4/Development"

From EGIWiki
Jump to navigation Jump to search
Line 4: Line 4:
__TOC__
__TOC__


== New Developments ==
== Recent Developments ==
* Record Certification Status History - May 2011 https://rt.egi.eu/rt/Ticket/Display.html?id=939
* Record Certification Status History - May 2011 https://rt.egi.eu/rt/Ticket/Display.html?id=939
* Allow authorised operators to suspend sites at central level - March 2011 https://rt.egi.eu/rt/Ticket/Display.html?id=1094
* Allow authorised operators to suspend sites at central level - March 2011 https://rt.egi.eu/rt/Ticket/Display.html?id=1094

Revision as of 14:25, 24 May 2011

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Tools menu: Main page Instructions for developers AAI Proxy Accounting Portal Accounting Repository AppDB ARGO GGUS GOCDB
Message brokers Licenses OTAGs Operations Portal Perun EGI Collaboration tools LToS EGI Workload Manager


Back to GOCDB/Documentation_Index

Recent Developments

Release Status

GOCDB V4 was released in the last quarter of 2010, and represented a major functional re-write. Following its release a number of business logic issues/restrictions and new feature requests have been documented (43 in RT). Current work is focused on operational support, fixing of issues and re-developing code to accommodate new (post V4 release) requirements.


  • GOCDB4 Central Visualisation Portal
    • last released version: 4.0-4d6 (October 2010)
    • next release: TBD
  • GOCDB4 Input System
    • last released version: 4.0-4d6 (October 2010)
    • next production release: TBD
  • GOCDB4 Regional Module
    • last released version: 4.0-4d7 (October 2010)
    • next production release: TBD

GOCDB4 Improvements / Developments

See GOCDB/Release4/Feedback : This page groups all feedback received on the new system.

The list of [GOCDB development items is available in the EGI RT ticket tracker]

These are the developments we are currently working on. They come from the agreed development list, as defined by the Operational Tools Advisory Group (OTAG) who filters and prioritizes user requests.

As of May 2011, development plans for the next 12 months are focused on re-developing and refactoring the current system in order to accommodate newly emerging feature requests that cannot be easily implemented with the current system. These include;

  • Implement new ‘EndpointLocation’ objects in GOCDB to provide WSDL and service contact URLs for services such as UNICORE. This requires refactoring of the existing DB cardinality logic and of the XML Output module. See technical details: Media:GocdbGlue2UnicoreV2.pdf and the sample output xml files below:
<SERVICE_ENDPOINT>
  <PRIMARY_KEY>206G0</PRIMARY_KEY>
  <HOSTNAME>ral.ac.uk</HOSTNAME>
  <GOCDB_PORTAL_URL>https://localhost/portal/index.php?Page_Type=View_Object&object_id=206&grid_id=0</GOCDB_PORTAL_URL>
  <BETA>N</BETA>
  <SERVICE_TYPE>Classic-SE</SERVICE_TYPE>
  <HOST_IP>1.2.3.4</HOST_IP>
  <CORE></CORE>
  <IN_PRODUCTION>N</IN_PRODUCTION>
  <NODE_MONITORED>N</NODE_MONITORED>
  <SITENAME>GRID-LCG2</SITENAME>
  <COUNTRY_NAME>France</COUNTRY_NAME>
  <COUNTRY_CODE>FR</COUNTRY_CODE>
  <ROC_NAME>France</ROC_NAME>
  <URL>new://endpoint:4838/url</URL>
</SERVICE_ENDPOINT>
<SERVICE_ENDPOINT>
  <PRIMARY_KEY>198G0</PRIMARY_KEY>
  <HOSTNAME>test.host.com</HOSTNAME>
  <GOCDB_PORTAL_URL>https://localhost/portal/index.php?Page_Type=View_Object&object_id=198&grid_id=0</GOCDB_PORTAL_URL>
  <BETA>N</BETA>
  <SERVICE_TYPE>Classic-SE</SERVICE_TYPE>
  <HOST_IP>10.1.1.2</HOST_IP>
  <CORE></CORE>
  <IN_PRODUCTION>N</IN_PRODUCTION>
  <NODE_MONITORED>N</NODE_MONITORED>
  <SITENAME>BIGSITE</SITENAME>
  <COUNTRY_NAME>Switzerland</COUNTRY_NAME>
  <COUNTRY_CODE>CH</COUNTRY_CODE>
  <ROC_NAME>GermanySwitzerland</ROC_NAME>
  <URL></URL>
</SERVICE_ENDPOINT>


  • The GUI logic needs to be re-developed. Currently GOCDB4 uses a generic module for drawing a forms and GUI components that uses a single code path for all form based operations. In doing this, the code has become too rigid making it difficult to deal with exceptional circumstances on a per-page basis. This module will be replaced with a more flexible controller per page architecture with view templates. This is necessary to address the RT requirement requests (approximately half suggest GUI improvements).
  • The current role model may need to be updated and/or even re-written in order to cater for a finer grained permission model that is emerging as a new EGI requirement.
  • The object cardinality logic needs to be refactored to fix known issues, particularly Domain, Production-Status and Service-Endpoint objects.
  • Fix database transaction demarcation issues (e.g. on site creation Savannah 74860).
  • Explicitly indicate if all SEs of a site are in downtime through the PI
  • Redevelop the xml_output module to implement nested XML collections, probably using the Query2XML package. This is necessary because the existing XML Output module will only generate flat XML documents (e.g. that often map to individual DB entities). Currently SQL joins/associations between Sites, SEs and URLs cannot be represented as hierarchical/nested XML documents (for example, consider nesting multiple EndpointLocation objects/URLs in the ServiceEndpoint XML, see: Media:GocdbGlue2UnicoreV2.pdf).
  • New ‘tagging’ logic is required so that new data-scoping rules can be applied to GOCDB entities, allowing Sites, Services and other GOCDB data to be identified as either ‘EGI,’ ‘Local’ or ‘some other’ scoped data. This is required for the Regional-Synchronizing GOCDB so that only appropriately scoped ‘EGI’ data is published to the central instance while locally scoped data and other customisations can be excluded. See GOCDB/Release4/Regionalisation#1.29_Data_Grouping.2FScoping


development item Estimated release Estimated date
Provide a production quality package for GOCDB regional module 4.0d7  Oct 2010
Improvement of GOCDB failover system and backend replication  4.0.1  May 2011
New service endpoint URL associations for new service types (see above) ? April/June 2011
Re-develop GUI Logic (see above) ? Sept 2011 (EGI-Y2)
Update/refactor role model for finer grained permissions (see above) ? EGI-Y2
Data scoping by tagging GOCDB entities (see above) ? EGI-Y2
Regionalisation GOCDB/Release4/Regionalisation ? EGI-Y3
Work on GOCDB and Operations Portal common front end  ?  EGI-Y3
GOCDB interface to the dynamic information system (BDII/GluE)  ? EGI-Y3


Regionalisation

See GOCDB/Release4/Regionalisation plans and progress report page