Keywords Cloud Computing, Service Level Agreements (SLA), CloudSim, Monitoring & Controlling SLA Agent, JADE

Transcription

1 Volume 5, Iue 8, Augut 2015 ISSN: X International Journal of Advanced Reearch in Computer Science and Software Engineering Reearch Paper Available online at: Verification of Agent Baed Sytem for Monitoring and Controlling SLA in CloudSim Sarwan Singh Reearch Scholar, Sai Nath Univerity, Jharkhand, India Manih Arora Joint Director (Sytem) NIELIT, Chandigarh, India Abtract Cloud computing i an on-demand computing model where Cloud uer pay in per uage mode. Cloud uer avail ervice and Cloud ervice provider provide ervice. The ervice are provided on mutually agreed term and condition called Service Level Agreement (SLA). Thee term and condition are to be monitored during runtime to avoid any breach of trut between Cloud uer and Cloud ervice provider. A oftware agent baed monitoring tool i implemented and verified to monitor the SLA parameter that include reource being allocated during runtime and compare runtime value with the agreed parameter value. Thi paper preent the verification agent developed for Monitoring and controlling SLA, MACSLA. The working of agent i verified uing CloudSim where three virtual machine run. The agent generate alert in cae of any violation of reource allocation. Thi will help both Cloud Service Provider and Cloud uer in maintaining trut in the Cloud ervice being offered. Keyword Cloud Computing, Service Level Agreement (SLA), CloudSim, Monitoring & Controlling SLA Agent, JADE I. INTRODUCTION Cloud computing i an eential utility in today computing world. In thi on-demand computing model reource are made available on pay per ue bai, where trut between the Cloud uer and Cloud ervice provider i maintained by Service Level Agreement (SLA). Any violation in SLA parameter will impact the trut between the two. At runtime variou SLA parameter like RAM, Bandwidth MIPS, etc. aigned to Virtual Machine (VM) are monitored by a dynamic agent baed ytem [1] and alert are generated for any violation noted during run time. The agent baed ytem for monitoring and controlling SLA i implemented uing JADE and CloudSim with back end upport databae, MySQL. It i difficult to analye the performance of agent in actual environment, a it involve uage of hared reource with lot of Hardware. Thu imulation tool are becoming important and neceary for evaluation of Cloud computing model and agent baed model for calculating efficiency, reliability and performance. The verification of an agent i very important to acertain that the deign of agent i a per the requirement and it i performing the deired tak optimally. The verification proce of the agent require different tet cae. In view of thi, different tet cae have been identified and ued in verifying the working of agent for the purpoe of monitoring and controlling Multi level SLA. The paper ha been organized into five ection; ection II review the background and related reearch, ection III brief the verification approach, ection IV doe the analyi of output, followed by the concluion and cope for future work in ection V. II. BACKGROUND & RELATED RESEARCH a) Monitoring and Controlling SLA uing Agent Service Level Agreement (SLA) i an important document of agreement which maintain the trut relationhip between Cloud ervice provider and Cloud uer. Thi not only decribe variou SLA parameter wherea guarantee them with remedial action in cae of violation. For thi caue a oftware Agent baed methodology prove beneficial, and hence agent baed Monitoring and Controlling SLA (MACSLA) i modelled [2] [3]. The Monitoring and Controlling Agent (MCA) which orchetrate the whole proce and provide graphical interface to Cloud Adminitrator/Uer. The MCA ha two main procee underneath i.e. Term Collector (TC) and Term Monitor(TM). The main job of Term Collector (TC) i to collect agreed SLA parameter and their predeigned value from the databae. On the other hand, Term Monitor(TM) will collect SLA parameter value while Virtual Machine (VM) i running. The MCA will compare the value collected by TC & TM and generate alert accordingly. The databae which tore the pre-deigned/prenegotiated SLA parameter value i implemented uing MySQL databae [4]. b) Implementation of MACSLA Agent MACSLA agent i implemented uing Cloud imulation tool, CloudSim. CloudSim i a framework which allow, modelling, imulation and experimentation with the Cloud computing infratructure model [5]. The high level architecture of variou entitie involved in CloudSim i hown in Figure 1. The Cloud uer end the ervice requet to 2015, IJARCSSE All Right Reerved Page 926

2 Singh et al., International Journal of Advanced Reearch in Computer Science and Software Engineering 5(8), Augut- 2015, pp Data Center Borker which coordinate with Cloud Controller to create intance of Hot in DataCenter. Cloud Controller may coordinate more than one Data Center. Hot ha multiple VM running over it with different number of Cloudlet. Figure 1 : Architecture of variou entitie in CloudSim There are many clae like Cloudlet, Hot, Virtual Machine, etc. in CloudSim which erve a building block of CloudSim imulator. In MACSLA, clae available with CloudSim imulator are extended to experiment the violation of SLA. Commonly ued clae are dicued below: 1) Cloudlet: Thi cla model the Cloud-baed application, repreenting pre-aigned intruction length and amount of data tranfer. According to the load aigned to Cloudlet, it take time to complete it computational tak. 2) Data Centre: In a Cloud computing environment the infratructure level ervice offered by Cloud ervice provider are modelled by thi cla. Thi cla i ued to implement variou policie for allocation of bandwidth, memory, and torage device. 3) Data Center Broker: Thi cla mediate between uer and Cloud ervice provider depending on uer Quality of Service (QoS) requirement. Thi cla i ued to experiment application placement policie. 4) Hot: Thi cla repreent a phyical machine with memory, torage, number of core, etc. 5) Virtual Machine: Thi cla model an intance of a VM, which run on Hot, along with other VM (i any). Every VM ha it own memory, torage, proceor, etc along with proviioning policie. III. VERIFICATION OF MACSLA The implemented MACSLA i required to be verified for it functionality. The verification include identification of tet cae, generation of tet data and verification the functionality of agent implemented. The implemented agent i verified by integrating in imulator, CloudSim. The verification tep are detailed below : i) Identification of Tet Cae For the verification purpoe three Virtual Machine (VM) are created and deployed on two Hot. The configuration of VM and Hot are decribed in Table 1. Table 1: configuration detail of Virtual Machine and Hot Hot1 VM1 VM2 VM3 RAM (MB) Core MIPS Bandwidth 1,00,000 1,00,000 1,00,000 Hot2 RAM (MB) Core 2 2 MIPS Bandwidth 10,00,000 10,00,000 Baed on VM and Hot, eight tet cae are identified to verify MACSLA. The outcome of each tet cae would be either no violation or violation. The load i varied in each tet cae to know the outcome. The eight different tet cae and their outcome decribed in Table 2: Table 2 : Tet cae for three Virtual Machine Tet Cae VM1 VM2 VM3 1 Normal Load Normal Load Normal Load No SLA Violation No SLA Violation No SLA Violation 2 Over Load Normal Load Normal Load SLA Violation No SLA Violation No SLA Violation 2015, IJARCSSE All Right Reerved Page 927

3 Singh et al., International Journal of Advanced Reearch in Computer Science and Software Engineering 5(8), Augut- 2015, pp Normal Load Over Load Normal Load 3 No SLA Violation SLA Violation No SLA Violation Normal Load Normal Load Over Load 4 No SLA Violation No SLA Violation SLA Violation Over Load Over Load Normal Load 5 SLA Violation SLA Violation No SLA Violation Over Load Normal Load Over Load 6 SLA Violation No SLA Violation SLA Violation Normal Load Over Load Over Load 7 No SLA Violation SLA Violation SLA Violation Over Load Over Load Over Load 8 SLA Violation SLA Violation SLA Violation ii) Tet Data The tet data i generated in view of tet cae identified and deired outcome. The tet data i generated i uch a way that it hould fall in one of tet cae identified. The tet data generated (randomly) hown in Table 3 including the load on each virtual machine in the form of cloudlet. Table 3 : Tet data for each VM in different Tet Cae Tet Cae VM1 VM2 VM3 Remark (cloudlet count) (cloudlet count) (cloudlet count) No violation Violation in VM Violation in VM Violation in VM Violation in VM1 and VM Violation in VM1 and VM Violation in VM2 and VM Violation in VM1, VM2 & VM3 iii) Verifying Functionality of Agent The MACSLA agent [6] during runtime aign the Cloudlet to the Virtual Machine(VM).The code nippet to aign cloudlet to VM i given in Table 4. Table 4: java code nippet to aign cloudlet to VM // etcloudlettovm(cloudletlit, VMID, tart offet in cloudletlit, // end offet in cloudletlit); etcloudlettovm(cloudletlit, 1, 1, 7); etcloudlettovm(cloudletlit, 3, 8, 12); etcloudlettovm(cloudletlit, 2, 13, 15); The load on VM 1 i increaed by aigning more than 7 cloudlet a hown in the code nippet in Table 5. Table 5: java code nippet to aign cloudlet to VM // etcloudlettovm(cloudletlit, VMID, tart offet in cloudletlit, // end offet in cloudletlit); etcloudlettovm(cloudletlit, 1, 1, 7); etcloudlettovm(cloudletlit, 3, 8, 12); etcloudlettovm(cloudletlit, 2, 13, 15); etcloudlettovm(cloudletlit, 1, 16, 24); IV. ANALYZING THE OUTPUT The output after applying tet data for Tet Cae 1 i analyed. The cloudlet aigned to each of the VM are given in Figure 2. Under thi cenario, none of the VM violate the agreed SLA parameter. The Figure 2 ha three graph w.r.t time for each VM. The firt graph i for RAM v Timetamp, econd i for Mip v Timetamp and third i Bw v Timetamp. Each graph ha two parameter plotted, one repreenting agreed SLA parameter and other for SLA parameter being allocated to VM on runtime. 2015, IJARCSSE All Right Reerved Page 928

4 Singh et al., International Journal of Advanced Reearch in Computer Science and Software Engineering 5(8), Augut- 2015, pp Virtual Machine 1 Virtual Machine 2 Virtual Machine 3 No. Of cloudlet aigned 7 No. of cloudlet aigned 3 No. of cloudlet aigned 5 Figure 2 : Tet cae 1- VM1, VM2,VM3 are not violating SLA Later, the load in VM1 i increaed to verify Tet Cae 2. The effect of aigning 9 more cloudlet are depicted in Figure 3. The VM2 and VM3 ha ame load/cloudlet running on them, therefore SLA i not violated and remain a before. Figure 3 : Tet cae 2 VM1 violate the SLA Similarly, load on VM are increaed a per the Tet Cae and further reult are analyed a hown in the Figure 4. All the VM tart violating the SLA. Virtual Machine 1 No. Of cloudlet aigned 13 Virtual Machine 2 No. of cloudlet aigned 12 Virtual Machine 3 No. of cloudlet aigned , IJARCSSE All Right Reerved Page 929

5 Load / Cloudl et Load / Cloudl et Load / Cloudl et Singh et al., International Journal of Advanced Reearch in Computer Science and Software Engineering 5(8), Augut- 2015, pp Figure 4 : Tet cae 8-VM1, VM2,VM3 are violating SLA The uer interface created in JADE [7] a hown in Figure 5 prompt the variou SLA parameter value being collected by Term Monitor(TM) and compare it with deired value aved in databae by Term Collector (TC). The column howing Required Value i aved in databae by TC, the Demanded Value i aved in databae by TM and if any violation the third column how true along with background color changing to red, otherwie it how fale with white background. Figure 5 : Agent UI developed in JADE The eight tet cae identified are verified in the imulated environment uing CloudSim. It i found that the SLA violation take place with increae in load on Virtual Machine in context to parameter under obervation like RAM, MIPS, and Bandwidth. The complete reult for all the tet cae with load/cloudlet being aigned to each VM i hown in Table 6. Tet Cae Table 6 : Reult of SLA violation in different tet cae for three Virtual Machine VM1 VM2 VM3 SLA Violation SLA Violation SLA Violation RAM MIPS Bandwidth RAM MIPS Bandwidth RAM MIPS Bandwidth 1 7 No No No 3 No No No 5 No No No No No No 5 No No No 3 7 No No No No No No 3 No No No , IJARCSSE All Right Reerved Page No No No No No No No No No 5 No No No 12 10

6 Singh et al., International Journal of Advanced Reearch in Computer Science and Software Engineering 5(8), Augut- 2015, pp V. CONCLUSION The Monitoring And Controlling SLA (MACSLA) ha proved that any violation in SLA i highlighted a well a recorded in databae which aure Cloud uer that he i getting what ha been demanded and maintain trut relationhip between Cloud uer and Cloud ervice provider. REFERENCES [1] Sarwan Singh, Manih Arora, Implementation of Agent Baed Sytem for Monitoring and Controlling SLA in Cloud Environment, IJEBEA, Augut 2015 [2] Sarwan Singh, Manih Arora, Deign of Agent Baed Sytem for Monitoring and Controlling SLA in Cloud Environment, IJATES, Volume No 03, Special Iue No. 01, March 2015 [3] L. Taquier, S. Venticinque, R. Avera, and B. Di, Agent Baed Application Tool for Cloud Proviioning and Management, 3rd International Conference on Cloud Computing (CLOUDCOMP 2012), Wien, Autria, September 24 26, 2012 [4] MySQL, Available at acceed on Augut 16, 2015 [5] Rajkumar Buyya, Rajiv Ranjan, Rodrigo N. Calheiro Modeling and Simulation of Scalable Cloud Computing Environment and the CloudSim Toolkit: Challenge and Opportunitie, {raj, rodrigoc}@ce.unimelb.edu.au, rajiv@unw.edu.au [6] K. M. Sim, Agent-baed Cloud Computing, IEEE Tranaction On Service Computing, Vol.5, No.4, pp.564,577, Fourth Quarter [7] Java Agent Development Framework, Available at acceed on Augut 16, , IJARCSSE All Right Reerved Page 931