90 likes | 208 Vues
A detailed exploration of the software and hardware practices utilized in the GOC (Grid Operations Center) by Soichi Hayashi. This overview delves into the deployment of VM hosts, production systems, and internal services like LDAP and MySQL. It emphasizes key aspects such as backup strategies, service redundancy, installation scripts, and user-friendly frameworks designed for non-engineers. With a focus on PHP, Python, and Java technologies, this document aims to provide insights into effective software development and operational management in an academic environment.
E N D
Inside GOC Soichi Hayashi Software Engineer
Hardware • VM Hosts • Production (B-town & Indi) • Dev & ITB (B-town) • LDAP Server (389) • Internal.grid.iu.edu • VM Install scripts / data • Service soft-backup • IU Services • SVN, Footprint, etc..
Backup • Soft Backup (/usr/local/backup @internal) • MySQL Replication • All transitory files are periodically synced • Key configuration files are also synced • Hard Backup • TSM backup system running on internal
VM • Most services are redundant (DNS RR-ed) • Wget access secondary service if one is failing • Load balancing / “Higher” failure tolerance • No HA at this point • “Stemcell” • Default GOC node with DHCP, LDAP, etc • Master Install Script • Service Install Scripts • Download files / configs, then run install script • Pulls softback data from internal.grid
Install Script • Installs everything to setup a certain GOC service • Updated when service machine is updated
Software Development • Nothing fancy.. Really… (sorry!) • PHP/Python for POC, Java for production • MyOSG (PHP, MySQL, Java, Google Chart, Python, jQuery) • OIM (Java, MySQL, DivRep) • GOC Ticket (PHP, SOAP, MySQL, jQuery) • Others stuff in scripting languages
DivRep Framework • Simple user interface framework for Java • Easy to learn, easy to implement • In academic environment, not everyone is software engineer • Minimizes the required knowledge • Build stuff using what they know • Basic Java, Basic HTML, Bit of Servlet • Secret is in “Replacing Content” • Sacrifices bit of responsiveness for • Greatly simplified development / testing
Contact • hayashis@indiana.edu