INF Lecture plan

Transcription

1 INF5120 Model based System Development F13-1: ADM (Architecture Driven Modernisation (Reverse MDA)) Migration to SOA and Cloud computing F13-2: MDI (Model Driven Interoperability), Data and Service Interoperability Lecture Arne-Jørgen Berre INF Lecture plan Part I: SSI Service Innovation and Agile Service/Software Engineering Part II: SSMDE Model Driven Engineering Part III Model Driven Interoperability and ADM 1: 16/1: Introduction to Model Based System Development (INF5120) 2: 23/1: SIE I: Enterprise Architecture, Role modeling-collaboration and Value Networks Verna Allee (VNA) 3: 30/1: SIE II:: Business Process Modeling with BPMN 2.0 and Business Model Innovation - Peter Lindgren (BMI) 4: 6/2: SIE III: AT ONE User-oriented design with Use cases and user stories 5: 13/2: SIE IV: Service modeling with SoaML Service modeling - Design, patterns 6: 20/2: SIE V: Precise Modeing in UML with OCL and Design with DCI - Design, patterns 7: 27/2: MDE I: Software Process Model Frameworks Essence/SEMAT, SPEM, EPF and ISO Shihong Huang/Brian Elvesæter/Arne J. Berre 8: 5/3: MDE II: Metamodels, Domain specific languages and UML profiles (Franck Fleurey, Brian Elvesæter) 9: 12/3: MDE III: Metamodeling, MDLE and DSL Tools (EMF, GMF, ATL, Kermeta) (Franck Fleurey) 10: 19/3: MDE IV: Model transformations - MOFScript, QVT DSLs with examples (Franck Fleurey) 11: 26/3: MDE V: Method Engineering and CORAS UML profile-: DSL example (Arne J. Berre) 2/4, 9/4: EASTER 12: 16/4: MDE VI: User Interface Modeling WebRatio-WEBML, ESITO-Genova, OMG IFML (AJB, Knut Sagli) 13: 23/4: MDI I: SOA technologies, MDE for SOA (Accenture/NAV) (AJB, Ismar Slomic, Øystein Gisnås ) 14: 30/4: MDI II: Information Models, Semantics and Model Driven Interoperability (AJB, Dumitru Roman) 15: 7/5: MDI III: ADM and MDA/Migration to SOA/SaaS/Cloud and MDI, Model Driven Interoperability 16: 13/5: Conclusion and Summary for INF Preparation of Exam Exam: Monday June 4th, 2011, (4 hours) 2 1

2 INF5120 Oblig/Exercise plan : 16/1: None 2: 23/1: Guest lecture: Value Networks Verna Allee (VNA) 3: 30/1: Guest lecture: Business Model Innovation - Peter Lindgren (BMI) Establish groups 4: 6/2: AT ONE initial exercise overall approach for Oblig 1 myservicefellow 5: 13/2: Group presentation 6: 20/2: Group presentation 7: 27/2: Group presentation 8: 5/3: MDE Tools introduction Oblig 2 intro 9: 12/3: MDE Tools II - EMF 10: 21/3: MDE Transformation tools - Delivery of Oblig 1 11: 26/3: Walk through of Oblig 1 2/4, 9/4: EASTER 12: 16/4: Discussion on Oblig 2 part 1 and 2 13: 23/4: Discussion on Oblig 2 - part 2 and 3 14: 30/4: Discussion on Oblig 2 - part 3 14: 7/5: Discussion on Oblig 2 - part 3 15: 7/5: Oblig 2 presentations 16: 14/5: Oblig 2 presentations. Conclusion and Summary for INF Preparation of Exam, Example exam 2011 Exam: Monday June 4th, 2011, (4 hours) 3 Cloud Computing; where it is now and challenges 2

3 Content Definition and some main concepts Cloud computing technologies Opportunities and challenges Activities around cloud projects, standardization Conclusions 5 Convergence to Cloud Computing Utility Computing Rackspace, Terremark, Savvis, IBM Adaptive Data Centers IBM, HP, Sun Enterprise Apps Microsoft, IBM, Oracle, Tibco Cloud Computing Virtualization VMware, Citrix Desktop Apps Google, Zoho Desktop as a Service Simtone, Desktone Grids Univa Ud, Gigaspaces, IBM Infrastructure as a Service Amazon.com Software as a Service Saleforce.com Platform as a Service Google, Microsoft 3

4 Definition of cloud Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. U.S. Government's National Institute of Standards and Technology The term cloud is not new and backs up to 90s (telecom clouds). Microsoft adopted it in 2001 when presenting.net framework as an infrastructure of computers that make up the internet. Ideas on sharing resources, distributed computing and services are even older. 7 Cloud Computing Definition Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is composed of five essential characteristics, three service models, and four deployment models. 5: On-demand self-service, Broad network access, Resource pooling, Rapid elasticity, Measured Service 3: IaaS, PaaS, SaaS 4: Private, Community, Public, Hybrid NIST Definition of Cloud Computing, Draft version 15, Oct 7,

5 Three service models Client Service Application Platform Storage Infrastructure IaaS Paas SaaS 9 Service Model Overview Model Capability Provided Example Services SaaS Citizen Engagement (Wikis, Blogs, Data.gov) To use the provider s applications running on a cloud Government Productivity (Cloud infrastructure and accessible from various client based tools) devices through a thin client interface such as a Web Business Enablement browser (Salesforce.com) Enterprise Applications (Core Mission & Business Svcs PaaS To deploy onto the cloud infrastructure consumercreated applications using programming languages and tools supported by the provider (e.g., java, python,.net) Database and Database Management Systems Developer / Testing Tools Virtual Environments IaaS To provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications Computing Storage Application hosting 5

6 Government Cloud Framework Three main deployment models Public cloud Services are characterized as being available to clients from a third party service provider via the Internet. Private cloud It offers many of the benefits of a public cloud but data and processes are managed within the organization. Hybrid Cloud A hybrid cloud is a combination of a public and private cloud that interoperates. Part of the infrastructure is maintained by the organization itself where as it also acquires the services from public clouds. 12 6

7 Advantages and disadvantages Private cloud: full control of all the resources related to a cloud infrastructure. investing in computing and storage resources but also on the related software and maintenance activities. Public cloud: the cloud computing infrastructure and operational activities are offered and maintained by service provider; dependent upon service provider; little control of resources; security of the data that is stored on the public cloud is a concern. Hybrid cloud: an organization can choose to maintain their critical resources as private cloud and rely on the public clouds for non critical business operations. 13 Other solutions Community cloud It is controlled and used by a group of organizations that have shared interests, such as specific security requirements or a common mission. Virtual private cloud (VPC) Runs on top of the public cloud with the additional benefit to have customized network topology and security settings. Applications running on a VPC can take benefit of cost effective infrastructure of public clouds and security mechanism of private clouds. General concerns with public clouds: Where are services being hosted? Can you trust the service provider to adhere to regulations? How is data backed up and stored? 14 7

8 Moving between the models or building supply chains? Computing Applications Storage Internet Computing Applications Storage users Computing Applications Storage Applications Other enterprises Enterprise 15 New possibilities with the Cloud Storage in big Gartner suggests that in 2-5 years cloud will be the place for any serious data management. New business models and supply chains Virtualization, off-the-shelf processing power, datacenters in containers, new maintenance concepts, new payment models, end-to-end connectivity, ++ Health sector, energy management and other sectors with many actors will probably gain most of connecting all these actors. 16 8

9 Essential characteristics of cloud Rapid Elasticity Cloud bursting Reliability & availability Multi-tenancy Measured Service Pay per use Several providers with divergent technologies and some essential challenges Management and self* Runtime configuration Data management Privacy and security Business models Start-up cost ROI Customer needs Interoperability Strong industrial drivers in US with their de-facto standards 17 Main PaaS providers Google App Engine (2008) For design, development and deployment of web applications hosted on Google servers. Originally built around Python tools and now with Java API as well. The application is totally separate from the hardware infrastructure (server, operating systems, geographical location) necessary for the running of the application. This application communicates with the outside world through web queries (http and https). Windows Azure (Feb 2010) PaaS based on.net technologies. Database service based on SQL Server The architecture of a Windows Azure application is based on the assembly of components called roles, provided by the platform. Each role represents an aspect of the application and allows access to a set of predefined services. Both supporting public clouds. 18 9

10 Main IaaS providers Amazon Elastic Compute Cloud- EC2 (2008) Enables the client to dynamically create virtual machines, in other words, server instances that can be as physical machines. A client can create, run and stop server instances and pays as the servers are used; Public, and Private cloud (Virtual Private Cloud ); Amazon Service Web API (AWS). Amazon also provides SaaS services or partial PaaS services on its «Amazon Web Service». Other technologies such as open source solutions Eucalyptus, OpenNebula and OpenStack are EC2 compliant. Rackspace is behind Amazon in US. 19 Open source IaaS initiatives Eucalyptus platform (2007) OpenSouce model but sales licenses for an Enterprise Edition; Private cloud platform with hybrid support; Compatible with Amazon EC2 and related platforms; Amazon Service Web API (AWS). OpenNebula Developed in research projects and released; supported by RESERVOIR and now StratusLab; Private cloud, Hybrid cloud (cloudbursting) with Amazon EC2, and public cloud support (EC2). OpenStack Backed by Rackspace, NASA, Dell, Citrix, Cisco, Canonical and over 50 other organizations

11 Market share in US Other 20% Rackspace 8% IBM 5% Amazon 59% Joyent 4% Terremark 4% 21 Challenges regarding technologies Many platforms with different architectural approaches; especially PaaS: Recent technology : few «industrial» feedbacks on these approaches; APIs and services available are very different from one platform to another; Vendor lock-in problem. Little interoperability and flexibility for moving between these or from private to public and back. Europe is lagging behind the US; US has a more homogenous market with big IT suppliers, selfservice culture Trying to address some of the above these by Open cloud manifesto and several standardization organs

12 Challenges for users New architecture for applications Modularity, scalability, data management etc. Understanding required capacity and performance Understanding their resource needs, peaks, workloads, etc Estimating the required service level. Assessment of solutions and later testing their applications; Costing and pricing Resources, licenses, human cost of management. 23 Majors standardization activities ( Standards Organisations Open Grid Forum Members Microsoft, Sun, Intel, HP, AT&T, ebay etc Cloud Computing Interoperability Forum Cisco, Intel, Thomson Reuters, Orange, Sun, IBM, RSA etc Distributed Management Task Force The European Telecommunication Standards Institute (ETSI) Open Cloud Consortium Cloud Security Alliance IBM, Microsoft, Novell, Oracle, Sun, Vmware, EMC etc Telecom Cisco, MIT Lincoln Labs, Yahoo, various colleges ebay, ING, Qualys, PGP, zscaler etc Storage Networking Industry Association Object Management Group Dell, EMC, Oracle, Juniper Networks, Qlogic, HP, Vmware, Hitachi, NetApp OMG members 24 12

13 Unification Efforts Eucalyptus with Amazon Web Services API With New Scale, rpath, MomentumSI NASA and Rackspace (and other partners) OpenStack API Red Hat Delta Cloud API For Amazon, GoGrid and RackSpace Open Cloud Computing Interface (OCCI) for IaaS providers RackSpace, Oracle, OpenStack, OpenNebula Conclusions Divergent platforms, new technologies Lack of experiences, need for large scale use cases and experimental facilities Technical and non-technical challenges Data management, security and privacy, flexibility, interoperability, business models, legalization issues, +++ Standardization activities Important to follow (but these are also emerging) Relations to other initiatives such as Green IT, Grid, Future Internet, Smart cities,

14 ADM Architecture-Driven Modernization (Reverse MDA) IT Architecture 14

15 Business Architecture Business architecture models in OMG in the Zachman framework Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why) Scope (Contexts) SBVR List of things important to business List of processes that the business performs VDM List of locations which the business operates OSM List of organizations important to the business List of events/cycles important to the business BMM List of business goals/strategies Business (Concepts) System (Logic) Semantic Model ODM Logical Data Model Business Process Model Application Architecture Business Logistics System Distributed System Architecture BPMN CMPM Workflow Model Human Interface Architecture Master Schedule Process Structure Business Plan SBVR Business Rule Model Technology (Physics) IMM (CWM) Physical Data Model SoaML System Design UML Technology Architecture Presentation Architecture Control Structure DTFV Rule Design Component (Assemblies) Data Definition Program Network Architecture Security Architecture Timing Definition Rule Definition Operation (Instances) Data Function Network Organization Schedule Strategy 15

16 IT Architecture Ecosystem IT/Business architecture transformation 16

17 Modernization horse shoe model Modernization scenarios 17

18 ADM Framework ADM Standards in OMG 18

19 KDM & ASTM Pattern Recognition and SMM 19

20 Patterns: From Analysis to Implementation Analysis Design Implementation Architecture Patterns (Macro Architecture) Analysis (Domain) Patterns Design Patterns (Micro Architecture) Domain Framework Idioms (Language dependent patterns) (OO) Reusable Components Visualisation, Refactoring and Transformation 20

21 SINTEF projects REMICS (REuse and Migration of legacy applications to Interoperable Cloud Services); started in 2010, SINTEF lead, two SMEs and other research partners. Focus on migration to SOA and cloud and developing a CloudML langauge. NEFFICS (Networked Enterprise transformation and resource management in Future Internet enabled Innovation Clouds) Started in 2010, SINTEF lead, using SaaS platforms combined with an advanced innovation management software platform. IRMOS Developing IRMOS platform to facilitate real-time interactive applications over SOI 41 FP7 Obj. 1.2, call 5 VISION Cloud Led by IBM Haifa, Participants: SAP, Telefonica, Telenor, France Telecom, Siemens, Engineering,. Total cost 15.7 M, October 2010-September 2013 A powerful infrastructure for reliable and effective delivery of data-intensive storage services. Use cases in Media, Telco, Healthcare and Enterprise

22 The REMICS approach Model Driven Interoperability Service mediation for adaptation SOA and Cloud Computing Patterns applied, Legacy Components Replacement and Wrapping, Design by Service Composition Knowledge : REMICS KDM Business Process and Rules Components : SoaML Implementation : UML, U 2 TP Source Architecture Migrate Target Architecture for Service Cloud platform SoaML with REMICS extensions for Service Clouds, Links to Business Models Knowledge Discovery, Reverse Engineering Source code, binaries, documentation, users knowledge, configuration files, execution logs and traces. Recover Legacy Artifacts Validate, Control and Supervise Forward MDA through PIM 4 Cloud Service Cloud Implementa tion Model Transformation, Code Generation, Traceability RESERVOIR, Joyant, Amazon, Google, Microsoft Runtime for application management, Model Checking, Model - based Testing for validation 43 Project concept Migration of legacy systems to service clouds Model-driven modernization approach Model metrics Recovery Requirements engineering Migration Model-based testing Agile methodologies Model-driven Interoperability 44 22

23 REMICS challenges regarding cloud Whether to have private or public or hybrid cloud. Business models and scalability concerns. Which cloud platform to choose? What does it mean for the architecture? Data handling (reporting system), authorization for access to data, maintenance and adaptation of the systems Developing a platform independent model for cloud that hides technologies (and related standardization activities such as PIM4Cloud, Interoperability for cloud) 45 REMICS Metamodel extensions 23

24 How does it work? Recovery Code Reverse Engineering UML Model Componentiz ation SoaML Model Migration UML and SoaML models SOA and Cloud patterns application Service Mediation PIM4Cloud, deployment generation Service Cloud Application Validation and Control UML, SoaML, PIM4Cloud models Modelbased Testing Model metrication untime Performance measurement 47 Involved tools Recovery Netfective BluAge reverse engineering tool WUT Tale GUI recovery tool SOFTEAM Modelio reverse engineering tools SOFTEAM Architecture Componentization Tool for Modelio Migration SOFTEAM Patterns Designer Tool SOA and Cloud patterns application SINTEF Interoperability Framework WUT RedSeeds application generation tools SINTEF, SOFTEAM PIM4Cloud modeling and deployment generation UT Desktop to Cloud Migration tool Validation and Control FOKUS!MBT FOKUS!Metrino WUT RSL Testing Tool Open source libraries for Framework for performance measurement of 3-tier applications 48 24

25 Tools involved BluAge Reverse Engineering tool FOKUS!Metrino RSL Testing Tool WUT Tale GUI recovery tool FOKUS!MBT Modelio, PIM4Cloud, Componentization and Patterns Designer WUT, RedSeeds Interoperability Framework SINTEF, PIM4Cloud DSL UT Desktop to Cloud Migration tool 49 PIM4Cloud scope in the cloud Standardisation Groups OMG: UML, SOAML, CCM, PIM4CLOUD 50 25

26 PIM4Cloud audience Who needs to model cloud deployment scenarios? Application designers System/Software Analyst: in charge of the analysis of cloud related requirements (QoS, load balancing, distribution, security, ) and the specification on how the system should resolve them. System/Software Architects: in charge of the definition of the cloud deployment for the system to implement the requested features. Application deployment responsible 51 PIM4Cloud Concepts 52 26

27 PIM4Cloud Concepts IAAS/SAAS/PAAS Cloud Application Cloud Resource Cloud Provider Public/Private Cloud VirtualImage Instance Physical Infrastructure Resource 53 4 Modelling Prespectives Cloud resources used Characterisation and Configuration of resources Virtual Image Modelling Private cloud components 54 27

28 Job possibilities at SINTEF? If you enjoy Model driven development you might be interested to work as a research scientist at SINTEF in particular related to European and international research projects such as REMICS! Shorter term work with latest technologies, - longer term work towards PhD research Contact: Arne.J.Berre@sintef.no or use arneb@ifi.uio.no CSI PhD position from mid 2012 Platform for Open Service Innovation CSI Center for Service Innovation with NHH, Architecture school of Oslo, UiO, SINTEF and partners Telenor, DnB, Posten, Tryg, Evry, Induct, Has a new PhD position in the area of Platform for Open Service Innovation - available from mid