PRAGMA 25 Working Group Report Resources Working Group Yoshio Tanaka (AIST) Phil Papadopoulos (UCSD)

Slides:



Advertisements
Similar presentations
PRAGMA – TeraGrid – AIST Interoperation Testing Philip Papadopoulos.
Advertisements

Kento Aida, Tokyo Institute of Technology Grid Working Group Meeting Aug. 27 th, 2003 Tokyo Institute of Technology Kento Aida.
Resource WG Breakout. Agenda How we will support/develop data grid testbed and possible applications (1 st day) –Introduction of Gfarm (Osamu) –Introduction.
National Institute of Advanced Industrial Science and Technology Experiences through Grid Challenge Event Yoshio Tanaka.
PRAGMA 17 (10/29/2009) Resources Group Pacific Rim Application and Grid Middleware Assembly Resources.
Resources WG Update PRAGMA 9 Hyderabad. Status (in 1 slide) Applications QMMD (AIST) Savannah (MU) iGAP (SDSC, AIST) Middleware Gfarm (AIST) Community.
Reports from Resource Breakout PRAGMA 16 KISTI, Korea.
Resources WG Update PRAGMA 10. Interoperability PRAGMA TG (ANL) Moving onto EGEE GGF GIN group Trust Enabled by APGrid PMA.
Resources WG Report Back. Account Creation Complaint –Too difficult to obtain user account on all resources Observations –Just ask Cindy and she will.
Resource WG Update PRAGMA 14 Mason Katz, Yoshio Tanaka, Cindy Zheng.
Resource WG Update PRAGMA 8 Singapore. Routine Use - Users make a system work.
Motivation 1.Application resources setup – make it easy 2.Transform PRAGMA grid – add on demand –Continue using Grid resources –Add cloud resources Current.
Steering Committee Meeting Summary PRAGMA 18 4 March 2010.
Resource WG Update PRAGMA 14 Mason Katz, Yoshio Tanaka, Cindy Zheng.
Resources WG Update PRAGMA 9 Hyderabad. Status (in 1 slide) Applications QMMD (AIST) Savannah (MU) iGAP (SDSC, AIST) Middleware Gfarm (AIST) Community.
Resource WG PRAGMA Mason Katz, Yoshio Tanaka, Cindy Zheng.
Demonstrations at PRAGMA demos are nominated by WG chairs Did not call for demos. We will select the best demo(s) Criteria is under discussion. Notes.
Resource/data WG Summary Yoshio Tanaka Mason Katz.
Resource WG Summary Mason Katz, Yoshio Tanaka. Next generation resources on PRAGMA Status – Next generation resource (VM-based) in PRAGMA by UCSD (proof.
A Proposal of Capacity and Performance Assured Storage in The PRAGMA Grid Testbed Yusuke Tanimura 1) Hidetaka Koie 1,2) Tomohiro Kudoh 1) Isao Kojima 1)
PRAGMA Futures Panel Philip Papadopoulos, UCSD All Opinions are mine and do not necessarily reflect those of my university, the US government or my cat.
VC Deployment Script for OpenNebula/KVM Yoshio Tanaka, Akihiko Ota (AIST)
Virtualizing Lifemapper for PRAGMA: Step 2 - The Computational Tier By Aimee Stewart, Cindy Zheng, Phil Papadopoulos, C.J. Grady University of Kansas Biodiversity.
PRAGMA Overview and Future Directions Workshop on Building Collaborations in Clouds, HPC and Applications 17 July 2012.
Virtualization in PRAGMA and Software Collaborations Philip Papadopoulos (University of California San Diego, USA)
GLOBAL VIRTUAL CLUSTER DEPLOYMENT THROUGH A CONTENT DELIVERY NETWORK Pongsakorn U-chupala, Kohei Ichikawa (NAIST) Luca Clementi, Philip Papadopoulos (UCSD)
PRAGMA19 – PRAGMA 20 Collaborative Activities Resources Working Group.
Day1 Update and discussion about charges – NCHC, NECTEC, UCSD, Osaka, AIST. Disaster Management Future Project.
PRAGMA Resources Group Updates Philip Papadopoulos (Interim Working Group Lead) Reporting on SIGNIFICANT WORK by a LARGE Cast of Researchers.
An OpenFlow based virtual network environment for Pragma Cloud virtual clusters Kohei Ichikawa, Taiki Tada, Susumu Date, Shinji Shimojo (Osaka U.), Yoshio.
PRAGMA19, Sep. 15 Resources breakout Migration from Globus-based Grid to Cloud Mason Katz, Yoshio Tanaka.
Experimenting with Persistent Live Video Streaming Service Kuang-Ching (KC) Wang Clemson University joint project with Parmesh Ramanathan University of.
 Cloud computing  Workflow  Workflow lifecycle  Workflow design  Workflow tools : xcp, eucalyptus, open nebula.
Building service testbeds on FIRE D5.2.5 Virtual Cluster on Federated Cloud Demonstration Kit August 2012 Version 1.0 Copyright © 2012 CESGA. All rights.
PRAGMA21 – PRAGMA 22 Collaborative Activities Resources Working Group.
PRAGMA20 – PRAGMA 21 Collaborative Activities Resources Working Group.
Personal Cloud Controller (PCC) Yuan Luo 1, Shava Smallen 2, Beth Plale 1, Philip Papadopoulos 2 1 School of Informatics and Computing, Indiana University.
FIM-related activities and issues being discussed in Japan 1.GEO Grid Yoshio Tanaka (AIST) 2.HPCI, GakuNin Eisaku Sakane, Kento Aida (NII)
Computer Science and Engineering - University of Notre Dame Jimmy Neutron CSE 40827/60827 – Ubiquitous Computing November 13, 2009 Project Presentation.
Cindy Zheng, Pragma Cloud, 3/20/2013 Building The PRAGMA International Cloud Cindy Zheng For Resources Working Group.
PRAGMA: Cyberinfrastructure, Applications, People Yoshio Tanaka (AIST, Japan) Peter Arzberger (UCSD, USA)
Resource WG PRAGMA 18 Mason Katz, Yoshio Tanaka.
National Institute of Advanced Industrial Science and Technology Introduction of PRAGMA routine-basis experiments Yoshio Tanaka
European Grid Initiative Federated Cloud update Peter solagna Pre-GDB Workshop 10/11/
DEV325 Deploying Visual Studio.NET Applications Billy Hollis Author / Consultant.
PRAGMA 17 – PRAGMA 18 Resources Group. PRAGMA Grid 28 institutions in 17 countries/regions, 22 compute sites (+ 7 site in preparation) UZH Switzerland.
Reports on Resources Breakouts. Wed. 11am – noon - Openflow demo rehearsal - Show physical information. How easily deploy/configure OpenvSwitch to create.
Kento Aida, Tokyo Institute of Technology Grid Committee meeting Aug. 25 th, 2005 Taipei Kento Aida.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
SBTeach Introduction School of Business Course Coordination System.
Resources Working Group Update Cindy Zheng (SDSC) Yoshio Tanaka (AIST) Phil Papadopoulos (SDSC)
Anonymity on Web Transaction Department of Computer Science Ball State University Research Methods - CS 689 Uday Adhikari 7 th Dec
Query Health Distributed Population Queries Implementation Group Meeting October 11, 2011.
Kento Aida, Tokyo Institute of Technology Grid Working Group Aug. 29 th, 2003 Tokyo Institute of Technology Kento Aida.
Kento Aida, Tokyo Institute of Technology Grid working group meeting Jan. 26 th, 2005 Bangkok.
Rick McGeer Chief Scientist, US IGNITE October 28, 2013.
SDN/OPENFLOW IN LHCONE A discussion June 5, 2013
Kento Aida, Tokyo Institute of Technology Joint Meeting Grid activities committee and Grid working group Jan. 28 th, 2004 Honolulu.
PRAGMA19 – PRAGMA 20 Collaborative Activities Resources Working Group.
PRAGMA 25 Working Group Updates Resources Working Group Yoshio Tanaka (AIST) Phil Papadopoulos (UCSD) Most slides by courtesy of Peter, Nadya, Luca, and.
CON8473 – Oracle Distribution of OpenStack Ronen Kofman Director of Product Management Oracle OpenStack September, 2014 Copyright © 2014, Oracle and/or.
Canadian Bioinformatics Workshops
Pacific Rim Application and Grid Middleware Assembly (PRAGMA)1:
Update on revised HEPiX Contextualization
StratusLab Roadmap C. Loomis (CNRS/LAL) EGI TCB (Amsterdam)
Review of Last PRAGMA 24 Meeting
StratusLab Sustainability
Discussions on group meeting
Motivation and Objectives
Open on the student drive
Presentation transcript:

PRAGMA 25 Working Group Report Resources Working Group Yoshio Tanaka (AIST) Phil Papadopoulos (UCSD)

Agenda of breakouts Thursday 14:00-16:15 – Discussion: VC sharing Detailed demo by Luca and Built Discussion for improvements and next steps based on insights gained through the demonstration Friday 11:10-12:30 – Discussion: CI for Scientists + Establish a PRAGMA Experimental Network Testbed (ENT) Expedition Joint session with Tele Science Review Lifemapper scenario Discussion on PRAGMA ENT – What and how should we do and who will be leading. Friday 14:00-15:30 – Discussion: What services should PRAGMA provide? How users use PRAGMA Cloud? What persistent infrastructure should PRAGMA provide / use? – Github, Gfarm, Marketplace What kind of services (data, computing, etc.) are available?

Summary of Breakout 1 Figured out issues gained through the experiments. – Took long time for booting on OpenNebula. This is because of the large VM image of Lifemapper. – The design of pragma_boot is tightly bound to Rocks, which may not be easy for OpenNebula to follow. – Need to provide simple documents/manual for users so that users can understand how to use PRAGMA Cloud. Next steps (by PRAGMA 26) – Experiments by more applications. – Write simple document/manual. – Increase the stability for OpenNebula – Merge code on Github – Implement more drivers AIST will do it for CloudStack Will anybody do it for OpenStack? UCSD for EC2?

Summary of Breakout 2 Goal of this breakout: figure out the followings – ENT issues Identified goals based on the proposal by Jim List interested communities/people and related activities – GENI, APAN FITWG, NSI, IPv6 – UF, Osaka/NAIST, UCSD, JLU, CNIC, NCHC, (AIST) We should updates information of PRAGMA resources and their service level. People – Tsugawa-san, Shimojo-san, and Ichikawa-san will be a co-leads. Use cases – Lifemapper – SDN-enabled SAGE for visualization Set schedule and milestones – Clarify necessary steps for joining the testbed. Necessary hardware/software, etc. – Implement a use case by the driving sites. – BD issues Use SDN for – Access control of restricted data. – Moving large quantity of data – avoid registration of IP addresses.

Summary of Breakout 3 Friday 14:00-15:30 – Discussion: What services should PRAGMA provide? How users use PRAGMA Cloud? – Should provide documents/manuals – One idea is to create a video for the introduction. – As the first step, students present demos and record. What persistent infrastructure should PRAGMA provide / use? – Avoid complex process of account mgmt. -> Science gateway – Use Github – Decide something about distributed storage/filesystem between now and the end of Jan. – Marketplace » Implement access control mechanism. » Develop GUI for Linux. » Design shared key mechanism for using Gfarm as a backend filesystem Provide information for users. – Renew resource information on github. Ask each site to provide and updates resource information by itself. – A service catalogue. Could be on github.