From ddea7a87e4b2a9889b2037359e24654f7f1178c5 Mon Sep 17 00:00:00 2001 From: Nikolaus Huber <nikolaus.huber@uni-wuerzburg.de> Date: Wed, 30 Jul 2014 09:29:04 +0000 Subject: [PATCH] git-svn-id: https://se1.informatik.uni-wuerzburg.de/usvn/svn/code/DMM/trunk@16288 9e42b895-fcda-4063-8a3b-11be15eb1bbd --- .../multiple_customers/readme.txt | 34 +++++++++++-------- 1 file changed, 19 insertions(+), 15 deletions(-) diff --git a/Examples/BlueYonder_Case_Study/multiple_customers/readme.txt b/Examples/BlueYonder_Case_Study/multiple_customers/readme.txt index 6d459466..e2db30b6 100644 --- a/Examples/BlueYonder_Case_Study/multiple_customers/readme.txt +++ b/Examples/BlueYonder_Case_Study/multiple_customers/readme.txt @@ -1,16 +1,20 @@ -Phase 1 -1. Set correct path to properties file -2. Adjust settings - 2.1. Set event in properies file to WorkloadUpdate-CustomerB - 2.2. Set latestObservation in PDR to observations.0 -3. Start adaptation -4. Check results (resoure landscape model). PS_CustB should have one more PS instance. +== 1st Adaptation Phase (customer B increases workload)== -Phase 2 -1. Set event in properies file to SLAviolated-CustomerA -2. Set latestObservation in PDR to latestObservation="//@observations.1" -3. Check results --> Applied tactic 1: IncreaseResourcesOfCustomerB. Result ID: NoResult. Successful: true. - Applied tactic 2: IncreaseResourcesOfCustomerA. Result ID: NoResult. Successful: false. - Applied tactic 3: MigrateResourcesOfCustomerA. Result ID: NoResult. Successful: true. - Applied tactic 4: MigrateResourcesOfCustomerA. Result ID: NoResult. Successful: true. - PS1 + PS2 of CustA are now on desc4 \ No newline at end of file +The first adaptation phase is triggered because customer B has increased its workload which will lead to an SLA violation. The adaptation framework and the modeled adaptation process can be used to find a new system configuration as follows: + +* Check if the paths to the model files are correct +* Set event in the by-multiple_customers.properies file to WorkloadUpdate-CustomerB (This event indicates that customer B has increased its workload) +* Set latestObservation in the performance data repository by-multiple_customers.pdr to observations.0 (latestObservation="//@observations.0"). This is necessary because performance data is stored in the repository. +* Start adaptation with + java -jar <path/to/your/adaptation_framework.jar> by-multiple_customers.properties +* Check the results. The resource landscape model by.resourcelandscape should show one more prediction server instance for customer B (PS_CustB). + +== 2nd Adaptation Phase (SLA of customer A violated) == + +Since the workload of customer B increased and required a new prediction server instance, the SLA of customer A are violated. We can use the adaptation framework to solve this as follows: + +* Set event.type in the by-multiple_customers.properies file to SLAviolated-CustomerA (indicates SLA violation) +* Set latestObservation in by-multiple_customers.pdr to latestObservation="//@observations.1". This observation contains the measurements for the system configuration which resulted from the previous adaptation. This has to be adjusted manually since currently the adaptation framework is based on the performance data repository. This step is obsolete as soon as the prediction module is ready. +* Start adaptation with + java -jar <path/to/your/adaptation_framework.jar> by-multiple_customers.properties +* Check the results. The resource landscape model should now have an additional prediction server instance for customer A. Both instances are deployed on a separate machine (desc4). \ No newline at end of file -- GitLab