Provisioning Deployment CDDLM-WG Configuration Description Deployment and Lifecycle Management

Provisioning/Deployment CDDLM-WG (Configuration Description, Deployment and Lifecycle Management) December 4, 2003 Takashi Kojo, NEC

Provisioning　Cycle Resource Allocation Plan Analysis/ Projection Deployment Execution /Monitor • Conceptual Loop for Optimizing Resource Allocation In Real World • The Cycle consists of variety of Loops • Long Loop like Annual/Quarterly Planning • Short Loop like Urgent Allocation for Surge Peak Load • Even Shorter Loop will be Implemented by Policy Automation of the Grid • Activities includes • Manual Intelligence • Manual Labor • System’s Automated

Provisioning Processes and Activities Business Processes Quarterly Plan New Customer Load Balancing Resource Allocation Plan Activities Analysis/Projection Deployment Execution/Monitor Etc.

Application and Infrastructure Analysis/ Projection Resource Allocation Plan Execution/ Monitor Analysis Application Projection Deployment DB Schema Provisioning Execution/ Monitor Deployment Infrastructure Provisioning Contents DBMS Resource Allocation Plan Applications App. Server Web. Server OS OS Server VLAN Set up Server OS VLAN Set up Server Network Switch Provisioning Target System (Ex. Web Three Tier) • Application: Grid Services, Legacy Applications, Web Contents, DB Schema • Infrastructure: Middleware (Application Server, Web Server, DBMS, …) Hardware (Server, Storage, Network Switch, Firewall, …)

Provisioning with Policy Automation ＡＰ DATA Conf Deployment Model Configuration Template Res Alloc/Config AP Provisioning Cycle Deploy Periodical Load Pattern Failure Recovery Exec/Monitor Feedback Execution Model Config. Descripition Eval/Analysis DATA ･･･ M/W ･･･ OS Server OS ･･･ Server Provisioning Configuration Management Grid Network Target Configuration Monitor AP M/W OS Server DATA M/W OS Server ･･･ ･･･ Network Resource Allocation ★Automated Resource Allocation based on Policy on Load Change or Failure ★Automated Configuration, Deployment and Execution Fault Management, Performance Management Account Management, Security Management M/W OS

Scope of PE Provisioning Grid Application (Demand) Business Process Automation Infrastructure Grid Analysis/ Projection Business Process Infrastructure Provisioning Execution /Monitor 　 Application Grid Deployment Automation Scope of CDDLM Application Provisioning Resource Allocation Plan Infrastructure (Supply)

Program Execution Components Monitor Status Job Management Monitoring Service？ Register Scheduler Canididate set Generator？ Resource Reservation Resource Types • Data Access • Bandwidth • Server • Storage Initiate/Terminate Program Contents Container Deployment Request Data Provisioning？ DAIS? Demand Supply Resource Configuration Resource Broker Resource Manager Deployment Lifecycle Management Scope of CDDLM WS-DM(CMM) Job Factory? Job Service? Program Contents Container

CDDLM (Configuration Description, Deployment and Lifecycle Management) CDDLM Wrapper Initiate/Terminate Lifecycle Management Class Files Web Contents Web Server Composition App. Server Application DB Server DB Schema XML based Component Description Deployment

End of OGSA-WG

CDL to Deployable Format Deployment Contents Front End Language Program: Class Files, … Web Contents: HTML, JSP, … DB Contents: Schema, … CDL 4 Unresolved References = XML-CDL Resolved References CDL 3 UR-CDL RR-CDL SF-CDL XML Based CDL Keyword XML Tag Resolve XML Based CDL Transform Deployment Contents Format (Extended JAR) Deployed Contents (Target Environment)

Use Case: Resource Broker and CDDLM Configuration Description UR-CDL (Host Names: Unresolved Parameter) Host Machine Broker Param Definition CDL Allocation Component (Host Name : IP Address Pairs) Agreement Resource Requestor (Client) Gather & resolve Deployment Contents IP Addresses Allocated RR-CDL

XML-based CDL based on Smart. Frog

Simple Mapping of SF syntax to XML . . . . . Component Vector

Example (manual pp. 13 -14)

Reference Model • Alternatives: – Smart. Frog Reference • use as-is (ROOT, PARENT. . ) • uri like syntax – Namespace – XPath/XPointer

Smart. Frog Reference Example (Manual p. 16)

The Top Level Definition: sf. Config • Instead of stating: – • we can define – • as the top level definition . .

Component Model (Prim, Compound) can be

sf. Class • Component should be defined as Service instead of Java class • Reference should be service URI instead of Java class name – Not: – But:

Component Definition Example (Manual pp. 36 -37)

Issues • Reference Model – Smart. Frog reference model can be used – But we should make best use of Namespace and XPath/XPointer (to avoid reinventing wheels) • Component Model – Components should be services instead of Java classes – The interface (sf. Deploy(), etc) should be redefined as WSDL