HORIZON2020 FRAMEWORK PROGRAMME TOPIC EUK

Transcription

1 HORIZON2020 FRAMEWORK PROGRAMME TOPIC EUK Federated Cloud resource brokerage for mobile cloud services D5.4 Hybrid Infrastructure Management: Software Prototype Project acronym: BASMATI Project full title: Cloud Brokerage Across Borders for Mobile Users and Applications Contract no.: Workpackage: 5 Dynamic Brokerage and Federation: Realization Editor: Songwoo Sok ETRI Author(s): Jamie Marshall Amenesik Authorized by Doc Ref: 5.4 Kim Baul Songwoo Sok Young Woo Jung Konstantinos Tserpes Innogrid ETRI ETRI ICCS Reviewer K. Tserpes ICCS Dissemination Level BASMATI Deliverable 5.4 Page i of vi

2 Document History Version Date Changes Author/Affiliation v TOC Songwoo Sok/ETRI v Changed TOC, Filled the contents Songwoo Sok/ETRI Jamie Marshall/Amenesik v Changed to fit for demo video Songwoo Sok/ETRI Jamie Marshall/Amenesik v Remove chapter 5, add installation Songwoo Sok/ETRI guide v Add Installation and Deployment Songwoo Sok/ETRI Guide v.0.9_kt Review version Konstantinos Tserpes/ICCS BASMATI Deliverable 5.4 Page ii of vi

3 BASMATI Glossary Term/Acronym Definition Mobile cloud services CP CSP Cloudlet Edge resources Online services offered by cloud resources to support mobile apps. The backend of the mobile apps. Cloud Provider. The actor that provides the cloud infrastructure/resources, such as VMs Cloud Service Provider. The actor that provides cloud services on top of a rent infrastructure from a CP Limited capacity infrastructures with virtualization capabilities, often used to support a limited amount of users or perform a limited set of operations on behalf of the central cloud infrastructure that hosts the complete application Resources aimed to operate specialized functionality, located at the "edge" of the network infrastructure, thus, closer to the end users. Examples are (clusters of) RaspberryPis or cloudlets BUDaMaF KE DM RB MVD DASFEST ACE BEAM ASP Brokering End user Offloading QoE BASMATI Unified Data Management Framework Knowledge Extractor Decision Maker Resource Broker Mobile Virtual Desktop An 3-day long music festival taking place in Karlsruhe, Germany every July Amenesik Cloud Engine. The cloud service deployment tool through which actual federation is achieved BASMATI Enhanced Application Model. An extension of the TOSCA specification Application Service Provider. A Federation user that rents resource services in order to provide an Application services to End-users The matchmaking support provided by BASMATI platform to decide about the best cloud resources to exploit for the execution of the back-end of BASMATI applications. This activity regards the placement of the services or data on computational resources and storages belonging to the cloud data centre and the cloudlets within the federation. A user who benefits the various application and infrastructure services provided by the Cloud. Within BASMATI, the most typical example is exploiting the Cloud federation via a mobile device (possibly a laptop) using specialized apps or a web browser. The ability of BASMATI platform supporting the runtime placement of the components composing the front-end of BASMATI applications on edge resources available nearby the end user. This activity takes place both when edge and mobiles exchange one each other their own workload or when such devices transfer some workload to the clouds or cloudlets. In BASMATI we often distinguish Front-end offloading, related to the mobile part of application, from Back-end offloading, concerning the server side of applications. The latter roughly translates to the known concept of Cloudbursting. Quality of experience. It is a measure of a customer's experiences with a BASMATI Deliverable 5.4 Page iii of vi

4 Service handover Situational Awareness service. It may be related to some aspects of the QoS and QoP, but can also take into account other metrics. Service handover refers to the activity of transferring an active service between two computational resources (e.g. Cloudlets) with minimal or no disruption on the availability of the service. Ideally, service handover is transparent with respect to the user. The ability of the BASMATI platform to recognise the situation characterising the actual combined status of users, applications and resources, aimed at achieving an effective and efficient management of applications and resources. BASMATI Deliverable 5.4 Page iv of vi

5 Executive Summary This prototype will deliver the BASMATI solutions for the management of the complete infrastructure and the realization of the federated environment based on the design of the BASMATI deliverable D5.3 "Hybrid infrastructure management: Design and specification". BASMATI Deliverable 5.4 Page v of vi

6 Table of Contents Executive Summary Introduction Relationship to Other Deliverables Scope of the prototype Software Prototype Testing Guide Preparation Deployment Guide Authentication Requirements Installation and Deployment Requirements Testing Procedures Prototype Demonstration Location Description Conclusion... 9 BASMATI Deliverable 5.4 Page vi of vi

7 1 Introduction This document presents the demonstration for the implemented software prototype based on D5.3. it includes description about demonstration video clips and test methods for the software prototype. 1.1 Relationship to Other Deliverables The Hybrid Infrastructure Management: Software Prototype deliverable has relations with other deliverables as shown in Figure 1.: (i) the design and architectures are defined in deliverable D5.3; (ii) the monitoring mechanisms for runtime adaptation is supported by the deliverable D3.4; (iii) the federation work among heterogeneous clouds and cloudlets are done by deliverable D4.2; (iv) all use case deliverables (D6.2, D6.3, D6.4) will be implemented based on this deliverable s results. Figure 1. Relationship to other deliverables 1.2 Scope of the prototype This deliverable is consisted of 3 components; Amenesik Cloud Engine or ACE, Application Controller, and Federation Monitoring. The ACE is the key component for federation among heterogeneous clouds, cloudlets and edges. It keeps all information of federated clouds and cloudlets, and supports OCCI standard interfaces to manage the infrastructures and services. The Application Controller is in charge of managing applications lifecycle over the infrastructures. It supports REST API to handle applications deployment status. The Federation Monitoring provides service and resource monitoring framework for runtime adaptation and SLA management for BASMATI. But, to support runtime adaptation and SLA BASMATI Deliverable 5.4 Page 1 of 9

8 management, it needs the help of other BASMATI components like SLA manager, Decision Maker, Resource Broker and Knowledge Extractor which are out of the scope of this demonstration. The Federation Monitoring itself is demonstrated in the BASMATI deliverable: D3.4 "BASMATI Service Monitoring Framework". Therefore, we skip the demo for Federation Monitoring in this deliverable. 2 Software Prototype Testing Guide To test the modules, they must be deployed on an internet accessible site and configured with proper variables to interact with other components of BASMATI. 2.1 Preparation Following components of BASMATI are needed to test the Hybrid Infrastructure Management software prototype. - Amenesik Cloud Engine: Manages clouds and cloudlets, Deploys applications on the infrastructures. - Application Repository: stores applications definitions and deployment status. - Application Controller: Manages applications lifecycle on ACE based on the deployment plans stored in Application Repository - Federation Monitoring: Collects performance values from deployed applications and resources. Those components must be running on internet-accessible nodes and configured correctly to interconnect among all components. The URLs of the components what was used for this demo video were like following table. Component ACE ACE OCCI Application Repository Application Controller Federation Monitoring URL Deployment Guide Since, the deployment procedures for ACE, Application Repository, and Federation Monitoring are described in D4.2 "Dynamic Cloud Federation: Software Prototype", D3.6 "BASMATI Serverand Client- side Applications Adaptation and Reconfiguration: Software Prototype" and D3.4 "BASMATI Service Monitoring Framework" respectively, only the Application Controller will be covered in here. BASMATI Deliverable 5.4 Page 2 of 9

9 2.2.1 Authentication The source codes of Application Controller are managed by using a private Git repository. To access it, following credential can be used: - URL: - Username: guest - Password: basmati_review Requirements Because the Application Controller depends on Docker [1] technology and Python Language, following environments are needed. OS Language Tools Linux based OS (ex. Ubuntu or later, CentOS 7 or later, ) Python 3 or later Docker and Docker-compose Installation and Deployment These are the steps for installation and deployment of the Application Repository. # git clone application-controller-etri.git ~/application_controller # cd application-controller # docker-compose build # docker-compose up If there are some errors, following configuration file should be modified. - applicaiton_controller/web/config/settings.py 2.3 Requirements Since testing programs have been written in Python3, they need python3-installed environment. For demo videos, we used following setups. OS Ubuntu x64 Desktop Language Python BASMATI Deliverable 5.4 Page 3 of 9

10 Processor Memory Storage Intel(R) Core(TM) i7-6700k 4.00GHz 8GB Samsung 960EVO 256GB SSD 2.4 Testing Procedures The source codes for test programs are available at following URL. - Testing programs can be executed on a command prompt. The commands for each tests are shown in following table. Test No. Test #1 Test #2 Test #3 Test #4 Test #5 command python3 d5_4_test1_list_cloud_providers.py python3 d5_4_test2_deploy_an_application.py python3 d5_4_test3_start_an_application.py python3 d5_4_test4_stop_an_application.py python3 d5_4_test5_undeploy_an_application.py 3 Prototype Demonstration The demonstration for this deliverable was made as a video, and it was uploaded on YouTube. This chapter describes about how to access the video and the details of the demonstration. 3.1 Location The demonstration video is composed with 5 parts. - #1 List managed Clouds and cloudlets - #2 Deploy an Application on the infrastructure - #3 Start the deployed Application - #4 Stop the started Application - #5 Undeploy the Application The URL of the video is BASMATI Deliverable 5.4 Page 4 of 9

11 3.2 Description In this part, we describe the results of testing program execution in detail. #1: List managed Clouds and cloudlets This shows the list of multiple heterogeneous clouds and cloudlets that consists hybrid infrastructure. This infrastructure is managed by ACE. A Python program was created to show the list and detail information. The list is shown in Fig 2. While the list includes some public clouds like Amazon, Azure and Google, it also has private cloudlets like openstack and opennebula. Figure 2 list of managed clouds and cloudlets of ACE Figure 3 The clouds and cloudlets list in OCCI interface of ACE BASMATI Deliverable 5.4 Page 5 of 9

12 #2: Deploy an Application on the infrastructure This is about deploying an application on the infrastructure using ACE. From this part, we used Application Controller s API to manage the application s life cycle. Figure 4 shows the result of deployment of mvd application. We can check the deployment result through ACE s WebUI like figure 5. Figure 4 Result of deployment of an application on the infrastructure Figure 5 "mvd" application is deployed on ACE #3: Start the deployed Application To run deployed application, START action must be issued. BASMATI Deliverable 5.4 Page 6 of 9

13 Figure 6 Result of "START" issue for the application After that, we can see the application is running in ACE. The status lamp for the application turned to green that means it is running now. Figure 7 The status of "mvd" application is green (means running) #4: Stop the started Application Before removing the application from ACE, it needs to be stopped first. Figure 8 Result of "STOP" issue for the application After STOP issued for the application, the status lamp will be changed to red on ACE s WebUI. BASMATI Deliverable 5.4 Page 7 of 9

14 Figure 9 The status is red (means it is not running) #5: Undeploy the Application To remove the application from the infrastructure, UNDEPLOY action should be issued to Application Controller. Figure 10 Result of "UNDEPLOY" action Then, the application will be disappeared in ACE s UI. BASMATI Deliverable 5.4 Page 8 of 9

15 Figure 11 The application is removed from the infrastructure. 4 Conclusion In this demonstration, we presented the Hybrid Infrastructure Management Software Prototype. It can manage multiple heterogeneous clouds and cloudlets and manage lifecycles of user applications on that infrastructure. The software can provide runtime adaptation features for deployed applications with the help of other components of BASMATI; I.e. Federation Monitoring, SLA manager, and Decision Maker. This software prototype will be used as a base component to construct the whole BASMATI platform. Also, it will provide the foundation for our target use cases like Das FEST, Tripbuilder and Mobile Virtual Desktop applications. BASMATI Deliverable 5.4 Page 9 of 9