1 / 21

Provisioning/Deployment

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.

drake-olsen
Télécharger la présentation

Provisioning/Deployment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. ProvisioningCycle 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

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

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

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

  6. Scope of PE Provisioning Grid Scope of CDDLM Application Provisioning Infrastructure Provisioning Application Grid Infrastructure Grid

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

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

  9. End of OGSA-WG

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

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

  12. XML-based CDLbased on SmartFrog

  13. Simple Mapping of SF syntax to XML <attributename=“Name” value=“Value”/> <attribute name=“Name1” extends=“Reference”> <attribute name=“Name2” value=“Value2”/> <attribute .../> .... </attribute> <attribute name=“Name”> <vector> <element value=“value”/><element>...</element> </vector> </attribute> Component Vector

  14. Example(manual pp.13-14) <attribute name="SFService"/> <attribute name="portNum" value="4047"/> <attribute name="hostname" value="adhost.smartfrog.org"/> <attribute name="administrators"> <vector> <element value="patrick"/> </vector> </attribute> </attribute> <attribute name="UseableService" extends="SFService"> <attribute name="portNum" value="4048"/> <attribute name="users"> <vector><element value="fred"/><element value="harry"/></vector> </attribute> </attribute>

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

  16. SmartFrog ReferenceExample <attribute name="sfConfig"/> <attribute name="foo“ ... /> <attribute name="bar” .../> <attribute name="baz"> <attribute name="ref1" reference="ROOT:sfConfig:bar:b"/> <attribute name="ref2" reference="foo:jan"/> <attribute name="ref3" reference="ref2"/> </attribute> </attribute> (Manual p.16)

  17. The Top Level Definition: sfConfig • Instead of stating: • <attribute name=“sfConfig”/> • we can define • <system/> • as the top level definition <system> <attribute name="d1" extends="def1"/> .... </system>

  18. Component Model(Prim, Compound) <attribute name=“xxx” extends=“Prim”/> <attribute name=“xxx” extends=“Compound”/> can be <component name=“xxx”/> <component name=“p” extends=“Printer”> <attribute name=“name” value=“myPrinter”/> </component>

  19. sfClass • Component should be defined as Service instead of Java class • Reference should be service URI instead of Java class name • Not: <attribute name=“sfClass” value=“classname”/> • But: <component service=“uri”/>

  20. Component Definition Example <component name="StatusMonitor" service="uri"/> <component name="LogMonitor" service="uri"/> <system service="uri"> <component name="log" extends="LogMonitor"/> <component name="status" extends="StatusMonitor"/> </system> (Manual pp.36-37)

  21. Issues • Reference Model • SmartFrog 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 (sfDeploy(), etc) should be redefined as WSDL

More Related