Asynchronous Provisioning Platform (APP)

Transcription

1 Service Catalog Manager - IaaS Integration Asynchronous Provisioning Platform (APP) 0

2 Overview Implementing an asynchronous provisioning service (e.g. for IaaS) most often requires complex implementation effort: Threaded / timer-based provisioning (as background operation) (including resume after system shutdown) Double-layered provisioning (provisioning on new created instance) Concurrency handling Persistency layer for service parameters (and custom data) Asynchronous handling of synchronously invoked operations (e.g. modify, delete, create users ) Manual interactions during provisioning Notification handling (e.g. mail-based exception handling) CT-MG provides an Asynchronous Provisioning Platform (APP) for simplifying the implementation of such provisioning services. 1

3 Basic Architecture Manual Notification (REST) Mail Server CT-MG Subscription Management Notification Handler Provisioning Service Proxy Timer APP Service Controller A Service Controller B Application Instance (A) Application Instance (A) Application Instance (B) DB DB Provisioning Service CT-MG APP Custom 2

4 Usage Scenarios A. Cloud Store-1 (APP operated by platform operator) Platform Operator CT-MG APP ISV-1 ISV-2 B. Cloud Store-2 (APP operated by service provider) Platform Operator CT-MG C. Enterprise Solution Store APP APP ISV-1 ISV-2 Platform Operator CT-MG APP App-1 App-2 3

5 Roles & Organizations APP supports separate roles for APP and controller administrators (CT-MG is the identity provider credentials are checked against CT-MG) BSS_USER_KEY/ BSS_USER_ID: Defines user account for basic CT-MG web service access Using a separate technical user account is recommended APP Admin: Any administrator of the organization defined by "BSS_USER_KEY Registering organization IDs for deployed controllers Controller Admin: Any technology manager of the organization registered for controller Access to APP notification handler Access to controller-specific configuration 4

6 Architecture Interfaces: Remote interfaces defined in separate project APPlatformController: APP core => Controller APPlatformService: Controller => APP core Lookup using JNDI Deployment: APP core as EAR file (fujitsu-bss-app.ear) Each controller as EAR file Persistence: APP core uses Hibernate/JPA Controllers should use only APPlatformService for persistence 5

7 Data Model configurationsetting: Key/Value store for global settings APP global setting (BSS URL, BSS user, mail server, ) Controller-specific settings (organization ID, controller configuration) serviceinstance: Representing the deployed service instances APP-specific information (flow state, locking, manual, ) CT-MG-specific information (subscription ID, organization ID, ) instanceparameter: Key/Value store for controller-specific instance data e.g. OS, #CPU, Memory in IaaS scenarios 6

8 Controller Development - Preparation Get access to the target system. Log in and understand the basics of service patterns (VMs, orchestrations, additional services) Get the current API documentation Try to provision certain basic patterns Define use cases in cooperation with stakeholders Understand available usage information, if relevant for charge back 7

9 Controller Development - Implementation Design service mapping from backend service to CT-MG Design parameter mapping according to defined use cases Implement component test cases (junit) Implement the controller Test and improve Implement configurable template as sample Implement a technical service as sample Create relevant documentation 8

10 Implementation - Tasks Key tasks: Define provisioning process Identify necessary steps and respective API Define flow states Implement dispatcher (communication with target API, stepping through the process flow, generating feedback) Questions: Are manual provisioning steps required? Are additional provisioning steps within a service instance required? 9

11 Implementation - Manual Steps Complex provisioning processes might include manual steps Operations not (easily) reachable by API e.g. tenant creation, documentation Controller detects need for manual steps Create resume callback with event service URL for platform service Notify responsible person by e.g. sending mail Pause status polling from APP by setting flag of instance status Notification handler gets resume request and restarts polling the controller => automated processing continues 10

12 Controller Development - Deployment Deploy the controller on the APP domain Register the controller on APP (via the APP Configuration UI) Apply the controller settings (either via SQL or the APP Configuration UI) Import the technical service Deploy the template Create a marketable service for the customer store on a test system Create a price model according to the available usage information Test subscribing, updating and terminating the service Start integration tests Create a marketable service for the productive customer store 11

13 Example VMware Service Subscription VMware VCenter (ESX Server) CREATION REQUESTED VMware APP Controller Creation of a new VMware instance is requested. CT-MG/APP WAITING_FOR SYSTEM CREATION CT-MG/BES asynccreateinstance ( ) CloneVM CREATING UPDATING New VMware instance is created by specified template (Clone). Custom VMware parameters are defined (CPU, RAM,...) getstatus( ) finished or failed? updateasyncsubscriptionprogress( ) ReconfigureVM PowerOnVM STARTING VMware is started. This will configure DNS specific settings as well (on guest system) COMPLETED completeasyncsubscription( ) RETRIEVE GUEST_INFO IP and hostname is retrieved. abortasyncsubscription( ) Guest Info (VM_Tools) MANUAL INTERACTION Additional manual operation of the IT department send IT department MANUAL OPERATIONS error FINISHED FAILED notification via servlet interface 12

14 Example VMware Service Termination VMware VCenter (ESX Server) VMware APP Controller CT-MG/APP WAITING_FOR SYSTEM DELETION CT-MG/BES deleteinstance ( ) DELETION REQUESTED RC: ok Remove Subscription STOPFOR DELETION Stop VMware instance PowerOffVM DestroyVM DELETING DESTROYED Destroy VMware instance COMPLETED (deletes service info) IT department error FAILED Send Send Notification Handler 13

15 Example VMware Service Update VMware VCenter (ESX Server) VMware APP Controller CT-MG/APP WAITING_FOR SYSTEM MODIFICATION CT-MG/BES modifyparameterset( ) MODIFICATION REQUESTED RC: ok STOPFOR MODIFICATION Stop VMware instance PowerOffVM UPDATING Updated VMware parameters are defined (CPU, RAM) ReconfigureVM PowerOnVM STARTING VMware is started. COMPLETED RETRIEVE GUEST_INFO Revalidate IP and hostname Guest Info (VM_Tools) IT department error FINISHED FAILED Send Send Notification Handler 14

16 15