FIll in sections below, then cut and paste into the report on research.gov. Due date: September 30th, 2014. I use Heading 1, 2, etc for the report sections. I use [TEXT GOES HERE] to indicate where you should put text. Text in red is instructions from reports.gov. ​ Milestones: please see what we submitted to Dan K and address these in the report: ​ https://docs.google.com/document/d/1Z7tuKSUjZCCQpwQOSIq3oURTfnHnWGFWx8-uIP139A w/edit#heading=h.jch3hpwyme5 For outreach, see https://docs.google.com/document/d/1KsgYZqF3aLU6Vs0Xf1i2Gu9_k5wlW81hxBNgjCt3Fg8/ed it#heading=h.v0qfwhj3h1bw Accomplishments For NSF purposes, the PI should provide accomplishments in the context of the NSF merit review criteria of intellectual merit and broader impacts, and program specific review criteria specified in the solicitation. Please include any transformative outcomes or unanticipated discoveries as part of the Accomplishment section. What are the major goals of the project? 8000 char limit. List the major goals of the project as stated in the approved application or as approved by the agency. If the application lists milestones/target dates for important activities or phases of the project, identify these dates and show actual completion dates or the percentage of completion. The overall goal of the SciGaP project is to develop a Science Gateway Platform as a service that can be used to power both participating gateways (UltraScan, CIPRES, NSG) as well as gateway community at large. To meet this, goal, we are implementing SciGaP as a multi-tenanted service hosted on a virtualized environment that provides a well-defined Application Programming Interface (API) for client gateways. Gateways can use SciGaP through this API to outsource the generic capabilities such as task execution on supercomputers and workflow management. Highlights this year include the XSEDE14 SciGaP tutorial, which provided focus for our development efforts and a highly visable venue for interacting with the science gateway community; the design and implementation of the Airavata API based on the analysis of a broad array of science gateway use cases compiled for XSEDE (https://www.ideals.illinois.edu/handle/2142/43883) and development patterns (Marru, S.; ​ ​ Dooley, R.; Wilkins-Diehr, N.; Pierce, M.; Miller, M.; Pamidighantam, S.; Wernert, J., "Authoring a Science Gateway Cookbook," Cluster Computing (CLUSTER), 2013 IEEE International Conference on , vol., no., pp.1,3, 23-27 Sept. 2013)); the development of a reference client implementation in PHP to provide a face for the API and an entry point for new developers; the deployment of the initial set of SciGaP services to support the XSEDE14 tutorial; and the integration of Airavata with the UltraScan Science Gateway. The following are the project’s recurring and Year 1 milestones. We summarize activities related to milestones as sub-bullets. Recurring Deliverables ● Engage in planned outreach activities ○ Presented Airavata API design and community architecture engagement at ApacheCon 2014, these API’s have resulted from SciGaP interactions. ○ Conducted gateway developer tutorial at CCGrid2014. ○ Conducted gateway developer tutorial at XSEDE14. ○ Pierce and Marru are participating in two Fall 2014 semester classes taught by Prof. Geoffrey Fox and Prof. Beth Plale, respectively. Course materials will be made available online as part of the IU School of Informatics and Computing’s Online Course strategy. ○ We mentored five Google Summer of Code 2014 student projects, including one with participation by PI Demeler (in addition to IU team). Details are listed here: https://cwiki.apache.org/confluence/display/AIRAVATA/GSoC+2014 ○ We are engaging new students in IU’s School of Informatics and Computing through “bootcamp” activities. Over 25 students have participated in overview presentations and are subscribed to the [email protected] mailing list. ​ ​ ○ The CIPRES project engaged one student from a women-only high school, who matriculated to UCLA in molecular biology in 9/2014. The CIPRES project also provided internships for two undergraduate students and two Master’s level students, all in computer science. One of these students has entered a PhD program at UIUC in August, 2014. ○ Three high school students participated in summer internship and worked on various NSG projects as a part of SDSC’s Research Experience for High School (REHS) program. NSG team hosted workshops at Society for Neuroscience (SFN November , 2013) annual meeting, at NEURON workshop ( June, 2014), and at Computational Neuroscience (CNS July, 2014) annual meeting. SFN and CNS had about 22 to 25 attendees and the NEURON workshop had 12 attendees. In addition NSG poster was accepted at both of these conferences and were presented by NSG team members. ● Conduct yearly gateway community user surveys. ○ The CIPRES project conducted a user survey in March to assess progress and trends in user needs. This year survey was emailed to 3200 users, and 800+ responses were received. ○ IU team members helped design and implement a major gateway survey as part of the related Science Gateway Institute, an NSF S2I2 project led by Nancy Wilkins-Diehr. An initial summary report was submitted to the NSF by the Institute. ● Follow 6-week release pattern for SciGaP software patches. ○ We released Apache Airavata 0.8-0.13 during the current period, with release 0.14 in preparation (anticipated by end of September). Year 1: SciGaP 1.0 Foundations ● Release Airavata 1.0 with API based on design documents and community input. ○ The Airavata API has been defined and validated through two tutorials, four Google Summer of Code projects, and integration with UltraScan. We are preparing release 1.0 based on this work and anticipate release in late October 2014, pending community vote. ● Design and begin implementing multi-tenanted SciGaP. ○ We have one accepted publication to CCGrid 2014 describing our approach to multi-tenanted security credential management, one accepted publication to the International Workshop on Science Gateways (2014) on the overall architecture, and one submitted publication to Gateway Computing Environments Workshop describing SciGaP’s multi-tenanted, API based approach and its implementation to support UltraScan’s usage requirements. ● Convert UltraScan to use SciGaP. ○ We completed conversion of UltraScan from legacy, pre-Airavata code for job submission and management in December 2013 but maintained the pre-existing interfaces. We are in the process of converting UltraScan-Airavata integration to use the new Airavata API and expect production usage by the end of September 2014, coinciding with a tutorial by PI Borries Demeler. ● Begin conversion of NSG to SciGaP. ○ NSG and CIPRES are branches of the same code base (the Workbench Framework). During Year 1, we have developed a common code base. CIPRES is already using this code base and NSG is in the process of adopting this code base. From analysis of this common code base, we derived two possible strategies for integrating the Workbench with Airavata. This was presented as a poster at XSEDE14. We also determined that it would be better to focus on integrating Airavata with this common code base, with evaluation through the CIPRES gateway, instead of NSG integration in Year 2. ● Initiate Net+ evaluation (see http://www.internet2.edu/netplus/service-phases.html). ​ ​ ○ We met with the Net+ team via teleconference and presented our project. It was determined that the Net+ team did not have the resources to help SciGaP develop the necessary business plan. Instead, the Net+ team recommended that we consult with Dr. Brad Wheeler (Indiana University’s Vice President for Information Technology and co-founder of Internet2’s Net+ activity) for recommendations and possible collaborations with faculty in Indiana University’s Kelley School of Business. We will follow up on this recommendation to meet with Dr. Wheeler. What was accomplished under these goals (you must provide information for at least one of the 4 categories below)? 8000 char limit for each of the 4 categories. For this reporting period describe: 1) major activities; 2) specific objectives; 3) significant results, including major findings, developments, or conclusions (both positive and negative); and 4) key outcomes or other achievements. Include a discussion of stated goals not met. 1) Major activities Project Wide: Our project-wide focuses this year were on developing a SciGaP API based on ​ detailed understanding of the CIPRES, NSG, and UltraScan use cases; implementing the API in Apache Airavata; standing up a preliminary version of the persistent, unified SciGaP services, and integrating UltraScan with these persistent services. In order to bootstrap the new collaboration between IU and SDSC team members, IU staff programmer Don Kushan Saminda Wijeratne was embedded with the SDSC development team. This effort is summarized in the XSEDE14 poster, “Evaluating CIPRES Science Gateway Integration Options with Apache Airavata” by Don Kushan Wijeratne, Mark Miller, Terri Schwartz, Suresh Marru and Marlon Pierce. IU and UltraScan team members also collaborated extensively on the API design and initial implementation in Apache Thrift with PHP client bindings. A two-day hackathon with UltraScan’s Gary Gorbet and the IU team in Bloomington in March 2014 was the keystone of this effort. Final integration with the API is being completed at the end of September 2014, coinciding with a tutorial in Juelich by UltraScan PI Borries Demeler. Apache Airavata: We released Airavata 0.10-0.13 through the Apache Software Foundation, ​ with 0.14 in preparation for the end of the month. Our major software development activities focused on defining the Apache Airavata API using Apache Thrift; a complete redesign of the Airavata Registry component to replace legacy data model definitions with data model bindings defined by Thrift; adding a new major component, the Orchestrator, to handle scheduling and simplify support for UltraScan, CIPRES, and NSG use cases; rewiring Airavata components to use the API Server and the Orchestrator; and reimplementing Airavata’s GFAC component to make it more fault-tolerant and elastic through the use of Apache Zookeeper.