CDL for BLAST Deployment

Slides:

Advertisements

Similar presentations

Computer Laboratory Virtualizing the Data Center with Xen Steve Hand University of Cambridge and XenSource.

Advertisements

1 Discussion on Lifecycle Management and Its Impact to CDL Jun Tatemura NEC Laboratories America Feb 5, 2004.

Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Managing Server.

An Approach to Secure Cloud Computing Architectures By Y. Serge Joseph FAU security Group February 24th, 2011.

Basic POSIX component for EMS May 12 th, 2006 Hiro Kishimoto.

OpenNebula VM ICOM5016 DATABASE SYSTEMS PROFESSOR: DR. AMIR CHINAEI PREPARED BY: PAUL BARTUS.

Presented by Mina Haratiannezhadi 1.  publishing, editing and modifying content  maintenance  central interface  manage workflows 2.

System Center 2012 Setup The components of system center App Controller Data Protection Manager Operations Manager Orchestrator Service.

Final Project – NFS and NIS jwbai. Computer Center, CS, NCTU 2 Goal master.passwd passwd group netgroup amd.conf userA, /nis/home/userA userB, /nis/home/userB.

Connecting OurGrid & GridSAM A Short Overview. Content Goals OurGrid: architecture overview OurGrid: short overview GridSAM: short overview GridSAM: example.

Windows Azure Conference 2014 Deploy your Java workloads on Windows Azure.

Puppet with vSphere Workshop Install, configure and use Puppet on your laptop for vSphere DevOps Billy Lieberman August 1, 2015.

E-science grid facility for Europe and Latin America LFC Server Installation and Configuration Antonio Calanducci INFN Catania.

Installation and Development Tools National Center for Supercomputing Applications University of Illinois at Urbana-Champaign The SEASR project and its.

A Web Laboratory for Visual Interactive Simulation of Epitaxial Growth Feng Liu University of Utah Recently, we have developed a prototype of web laboratory.

Exercise 4 – NFS and NIS Announced Date: 2007/12/11 Due Date: 2007/12/25.

CDDLM Configuration Description Language (CDL) Jun Tatemura NEC Laboratories America GGF13, March

VApp Product Support Engineering Rev E VMware Confidential.

Web Publishing By Alfred Leong, Ong Zhi Hong, Yeo Jun Kai.

1 Use of SDD in Grid Deployment Based on GGF CDDLM Jun Tatemura NEC Laboratories America Sept 14, 2005.

1 CDDLM: CDL Examples Jun Tatemura NEC Laboratories America Feb 1, 2006 GGF OGSA/CDDLM session.

AHM04: Sep 2004 Nottingham CCLRC e-Science Centre eMinerals: Environment from the Molecular Level Managing simulation data Lisa Blanshard e- Science Data.

1 Use of SDD in Grid Deployment Based on GGF CDDLM Jun Tatemura CDDLM WG member NEC Laboratories America Sept 13, 2005.

1 CDL for BLAST based on Chris’s JSDL document* OGSA-WG 14 March, 2006 *:

Computer Security Sample security policy Dr Alexei Vernitski.

Automating feature installations. A feature is a container of various extensions They contain a set of xml files which are delivered to the web front.

Let's build a VMM service template from A to Z in one hour Damien Caro Technical Evangelist Microsoft Central & Eastern Europe

Five todos when moving an application to distributed HTC.

16-26 June 2008, Catania (Italy) First South Africa Grid Training LFC Server Installation and Configuration Antonio Calanducci INFN Catania.

Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change.

Advanced Computing Facility Introduction

Platform as a Service (PaaS)

Creating Clusters in a Virtual Environment

Let's talk about Linux and Virtualization in 'vLAMP'

OGSA HPC cluster usecase for reference Model v.02

Platform as a Service (PaaS)

Product Training Program

Jun Tatemura NEC Laboratories Amercia GGF10, March 2004

CDDLM-WG discussions with OGSA-WG

Introduction to the Application Hosting Environment

A Cloudy Future of What? Jeff Hollingsworth.

Data Virtualization Demoette… ADO.NET Client

OGSA-WG EMS Architecture

Component and Deployment Diagrams

Data Storage Requirements

Serverless Architecture in Azure

TYPES OF SERVER. TYPES OF SERVER What is a server.

Application Deployment

Skill Based Assessment - Entity Framework -

Introduction to Docker

Managing Clouds with VMM

J2EE Application Development

Chapter 1: Intro (excerpt)

Microsoft Ignite NZ October 2016 SKYCITY, Auckland.

CRM 2016 Solutions and Package Deployer

TechEd /28/ :51 PM © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered.

Final Project Announce: Due:

Managing Services with VMM and App Controller

Final Project– NFS and NIS

DriveScale Log Collection Method of Procedure

Chapter 7 –Implementation Issues

gLite Job Management Christos Theodosiou

UML: Collaboration and Deployment Diagram

TechEd /23/2019 9:23 AM © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks.

Service Template Creation from the Ground Up

Service Template Creation from the Ground Up

Day 2, Session 2 Connecting System Center to the Public Cloud

Server & Tools Business

Presentation transcript:

CDL for BLAST Deployment Jun Tatemura CDDLM WG / NEC Laboratories America March 29, 2006 CDDLM WG

What to Deploy You have a code (BLAST) and data (database for BLAST) A data center provides A (computation) server That lets you deploy your code and mount a file system A file server That lets you deploy your data Deployment = make your code ready to run Assuming that provisioning is done (= you have reserved a server and a file server to use) File servers Server cluster BLAST DATA CDDLM WG

Components A Server A File Server <Server> <FileServer> Upload your file to a directory (that is referred to as “RootDir”) Mount a file system (ID) to a directory (Dir) Specify an environment variable (Env/@name) A File Server Upload your data (that is referred to as “ID”) <Server> <cmp:CommandPath …/> <cmp:CodeBase/> <Hostname cdl:lazy=“true”/> <RootDir cdl:lazy=“true”/> <FileSystem> <ID/> <Dir/> </FileSystem> <Env/> </Server> <FileServer> <cmp:CommandPath …/> <cmp:CodeBase/> <ID cdl:lazy=“true”/> </FileServer> These components (Servers and File Servers) are virtual entities. We don’t care how servers and file servers are physically located. They may or may not be dedicated machines. CDDLM WG

A BLAST System Your code/data is specified at cmp:CodeBase (using ACS?) Server has a reference to the file server, which is mounted at $ROOT/data After deployment, you can refer to BLASTSystem/Server/Hostname to locate a server You can run $ROOT/bin/blastall with –d $DATA/ncbiblast/nr how to coordinate with JSDL? <BLASTSystem> <Server cdl:extends=“d:Server”/> <cmp:CodeBase>blast.tar</cmp:CodeBase> <d:FileSystem> <d:ID cdl:ref=“/File/d:ID”/> <d:Dir>data</d:Dir> </d:FileSystem> <d:Env name=“ROOT” cdl:ref=“/Server/RootDir”/> <d:Env name=“DATA”>$ROOT/data</d:Env> </Server> <File cdl:extends=“d:FileSystem”> <cmp:CodeBase>blastdb.tar</cmp:CodeBase> </File> </BLASTSystem> CDDLM WG

A Template For BLAST If you want to deploy BLAST many times with different data, you may want to create a template to reuse <BLASTTmpl> <DataFile/> <Server cdl:extends=“d:Server”/> <cmp:CodeBase>blast.tar</cmp:CodeBase> <d:FileSystem …/> <d:Env …/> </Server> <File cdl:extends=“d:FileSystem”> <cmp:CodeBase cdl:ref=“/DataFile”/> </File> </BLASTTmpl> <MyBLAST cdl:extends=“tmpl:BLASTTmpl”> <tmpl:DataFile>blastdb.tar</tmpl:DataFile> </MyBLAST> CDDLM WG