1 / 5

GOC resilience

GOC resilience. John Gordon, STFC GridPP 22 microtalk. GOCDB Failover (1). Web portal Master instance at RAL, UK Replica instance at ITWM, Germany Database Master instance at RAL, UK Replica instance at CNAF, Italy Oracle Materialised Views Local backup instance at RAL, UK. Oracle 11g.

ima
Download Presentation

GOC resilience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. GOC resilience John Gordon, STFC GridPP 22 microtalk

  2. GOCDB Failover (1) • Web portal • Master instance at RAL, UK • Replica instance at ITWM, Germany • Database • Master instance at RAL, UK • Replica instance at CNAF, Italy • Oracle Materialised Views • Local backup instance at RAL, UK Oracle 11g Oracle 10g Oracle Xpress

  3. GOCDB Failover (2) 3rd party tools https://goc.gridops.org DNS alias End users operator Master web portal Replica web portal GOCDB-PI conf conf GOCDB-PI Master DB Backup DB Replica DB

  4. APEL • APEL is client software and a central respository that collects data from many sources, not just its own client. • Because it only receives and sends information daily it doesn’t really need many 9s • If a client fails to connect the same data is reposted next time it connects. • This is true for R-GMA and the Message Bus. • Even more true for the distributed architecture because there will be a hierarchy of repositories

  5. Local APEL Resilience • APEL servers will run on VMware ESX cluster • Allows images to be dynamically migrated between nodes for load balancing and maintenance • Automatic migration on failure of a physical node. • Could add same features as GOCDB but felt to be less necessary • Could duplicate flexible archiver to store into two independent databases. • R-GMA SPOF in current production version • Latest version allows multiple registries. • Similar with multiple message brokers.

More Related