GOCDB3 Progress Report

1. GOCDB3 Progress Report Matt Thorpe, Andy Newton COD 11 - Athens

2. Overview • Overview • Database development • Improvements • New Schema • Migration from GOCDB2 • hardware platform • Code development • Core classes • User Interface • Failover system • Summary COD-11, Athens

3. Database Development (1) • Improved back end database • Migrated schema from MySQL 4.x to Oracle 9i • Schema is now fully normalised with referential integrity • Supports storing information on VO related services on individual nodes • Expanded to include support for multiple grids, finer granularity for downtimes, more flexibility in user roles and more scope for storing historical data and metrics regarding sites, nodes and services • Includes a collection of PL/SQL functions to facilitate and simplify migration of third party applications to • Finalised schema available to view on GOC wiki at http://goc.grid.sinica.edu.tw/gocwiki/GOCDB3_development COD-11, Athens

4. Database Development (2) • schema finalised • May have minor changes during development but basic structure will not change • Library of PL/SQL functions is small at present but growing • All PL/SQL functions will be available to 3rd party application developers • Metadata migration tools complete • We have developed a migration package to convert metadata from the current production GOCDB2 system to the new framework. This will allow us to transition to the new framework smoothly and without loss of data • Migration between schemas takes less than 1 minute using this package COD-11, Athens

5. GOCDB3 – DB Schema COD-11, Athens

6. GOCDB3 Platform • Server status • The 2 new servers have been acquired and installed. However we are still developing the local failover system in collaboration with our sysadmins • Registered ‘gocdb.eu’ domain name • Development is currently underway on a third development platform • Software platform requirements have been finalised and will be deployed to the production machines shortly • Timescale for migration from development to production is anticipated to take approximately 1 week, however this is not currently a high priority COD-11, Athens

7. Code Development • Streamlined codebase • Complete rewrite of GOCDB2 code using PHP5 • Utilising ADODB database API for rapid development • Allows us to reduce coding overhead for DB operations • Allows the use of alternate databases during development • Can support this in production but due to failover requirements we will only be supporting Oracle. This may change in the future! • Improved error checking and exception handling architecture • Developed using Model – View – Controller architecture • Fully OO code • Shorter development lifecycle with modular code • Multiple abstraction levels enable rapid integration of new solutions COD-11, Athens

8. Code Development – Core classes • Core classes • Structure of the core classes has been completed but full functionality has not yet been achieved (i.e. we haven’t finished yet) • Improved QA process on business logic components • Multi-level unit and group testing framework • Structured testing schedule • New development environment facilitates improved debugging • We anticipate completion of these classes in around 4-6 weeks COD-11, Athens

9. Code Development - User Interface • Redesigned user interface • Professionally developed graphical look and feel • Navigation and layout is being completely redesigned for improved user experience and to make it more intuitive • Will include: • Breadcrumbs for faster navigation • Context sensitive help system • CSS style and layout (GOCDB2 used basic HTML / tables) • Utilising the PHP Smarty template engine to speed up interface development • Can support AJAX via the SAJAX framework • Implementation of basic interface is anticipated to take approximately 2-4 weeks, with more advanced features to follow COD-11, Athens

10. Code Development - User Interface Initial site design COD-11, Athens

11. Code Development - User Interface Test page with development banner, showing off the new rounded boxes COD-11, Athens

12. Failover system • Multiple DB, multiple UI architecture • Geographically distributed backend DBs • Oracle 9i or better • Distributed UI installs, not necessarily at same sites as the DBs • Software requirements for UI installs are modest: • Apache 2.x • PHP 5.x • PHP APIs (Oracle oci8, ADODB, smarty) • (These may come packaged with GOCDB3 for ease of install) • Need to investigate methods of failover between DBs and UIs as well as replication modes between Oracle resources COD-11, Athens

13. Summary • – New features • Improved availability with failovers • Support for multiple grids (not just EGEE) • Allows services to be associated with VOs • Allows resources (sites, nodes, services) to be logically grouped • More flexible roles / permission system allowing fine grained access from a whole grid down to a service level • Major improvements to scheduled downtimes • Can now be scheduled or unscheduled, have varying degrees of severity and be extended / shortened in an intelligent manner • Improved storage of historical data for metrics purposes • Simplified integration with third party applications through PL/SQL function library • Improved globalisation support COD-11, Athens

14. Thank you for listening Any questions? COD-11, Athens