Filip Krikava, profile picture
Uploaded byFilip Krikava
PDF, PPTX1,121 views

ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures

The document discusses the challenges and methodologies in integrating self-adaptive mechanisms into software systems, emphasizing the need for domain-specific modeling and feedback control loops. It introduces the Feedback Control Definition Language (FCDL) to enhance abstraction, reusability, and integration of adaptation engines. The work aims to address complexities in software architecture through systematic adaptation and monitoring, ultimately aimed at improving performance and reliability of systems.

Embed presentation

Download as PDF, PPTX
ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures SAC’14 - DADS 28.3.2014 Philippe Collet Robert B. France Colorado State University
 Computer Science Department USA Université Nice Sophia Antipolis I3S - CNRS UMR 7271
 France University Lille 1 / LIFL
 INRIA Lille
 France Filip Křikava
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures CONTEXT Jeff Kephart - Autonomic Computing: The First Decade, ICAC’11 keynote Electronic Retailer - Application Diagram • Ever growing complexity of computing systems • Taming this complexity by skilled IT professionals does not scale • New operation modes are needed
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures TOWARDS SELF-ADAPTIVE SOFTWARE SYSTEMS Monitoring Reconfiguration Decision Making sensors effectors Target System events actions measures decisions Feedback Control Loop (FCL) Systems that adjust themselves in accordance with some higher-level goals • response time • utilization • scheduling • concurrency policies
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Engineering of self-adaptive software systems is a challenge Designing an adaptation engine Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ CHALLENGES
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Engineering of self-adaptive software systems is a challenge Designing an adaptation engine Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ CHALLENGES Integrating an adaptation engine into a target system API LOGS CONFIGURATIONS COMMANDS AOP PROFILER • Consistent monitoring across all sensors • Coordination of adaptation action
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Engineering of self-adaptive software systems is a challenge Designing an adaptation engine Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ CHALLENGES Integrating an adaptation engine into a target system API LOGS CONFIGURATIONS COMMANDS AOP PROFILER • Consistent monitoring across all sensors • Coordination of adaptation action
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Integrating an adaptation engine into a target system Adaptation Engine Target System Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ API LOGS CONFIGURATIONS COMMANDS AOP PROFILER • Adhoc Implementations • Extensive handcrafting of non-trivial code • Cumbersome and error-prone • Accidental complexities CHALLENGES
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Integrating an adaptation engine into a target system Adaptation Engine Target System Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ API LOGS CONFIGURATIONS COMMANDS AOP PROFILER • Reusing and adapting existing work • Often target specific types of adaptation problems [Bertran’12] • Require the use of certain adaptation mechanism [Garlan’04] • Applicable to single domain [Rouvoy’08] or technology [Asadollahi’09] • Do not support remoting or complex control schemes [Adamczyk’08, Gorton’06] • Limiting their applicability CHALLENGES
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Derived requirements for integrating self-adaptation into software systems Generality • Domain-agnostic • Technology-agnostic • Explicit FCLs, their process and interactions • Verification support Visibility • Reusable FCL parts across adaptation scenarios Reusability • Remote distribution of FCL Distribution • Composition • Reflection Complex control • Prototyping • Automating Tooling REQUIREMENTS
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Monitoring Reconfiguration Decision Making sensors effectors Target System events actions measures decisions Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ API LOGS CONFIGURATIONS COMMANDS AOP PROFILER Generality Visibility Reusability Distribution Complex control Tooling CONTRIBUTIONS Feedback Control Definition Language1 The ACTRESS Modeling Environment2 Approach facilitating systematic integration of self-adaptive mechanisms into software systems through feedback control loops.
28.3.2014, SAC’14 - DADSACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures FCDL: Feedback Control Definition Language 1
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures FEEDBACK CONTROL DEFINITION LANGUAGE 1. Raise the level of abstraction 2. Fine-grained decomposition of FCL elements 3. Explicit interactions 4. Provide reflection and composition capabilities 5. Embed remoting Monitoring Decision Making Reconfiguration measures events decisions actions General Purpose Language (GPL)Generality Visibility Reusability Distribution Complex control
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures 1. Raise the level of abstraction 2. Fine-grained decomposition of FCL elements 3. Explicit interactions 4. Provide reflection capabilities 5. Embed remoting Domain-Specific Modeling FEEDBACK CONTROL DEFINITION LANGUAGE
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures 1. Raise the level of abstraction 2. Fine-grained decomposition of FCL elements 3. Explicit interactions 4. Provide reflection capabilities 5. Embed remoting Domain-Specific Modeling • Feedback Control Loop • Sequence of interconnected processes • Inputs x State -> Output • Reactive • Concurrent • Dynamic Monitoring Reconfiguration Decision Making sensors effectorsevents actions measures decisions FEEDBACK CONTROL DEFINITION LANGUAGE
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures 1. Raise the level of abstraction 2. Fine-grained decomposition of FCL elements 3. Explicit interactions 4. Provide reflection capabilities 5. Embed remoting Domain-Specific Modeling • Feedback Control Loop • Sequence of interconnected processes • Inputs x State -> Output • Reactive • Concurrent • Dynamic Monitoring Reconfiguration Decision Making sensors effectorsevents actions measures decisions • The Actor Model • Message passing actor networks • Message x State -> Message(s) • Reactive • Concurrent • Dynamic • Scalable • Remoting through location transparency actor actor actor FEEDBACK CONTROL DEFINITION LANGUAGE
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Monitoring Reconfiguration Decision Making sensors effectorsevents actions measures decisions Processor in input out output Effector in input Sensor out output Target System in input Controller in input out output Processor out output FEEDBACK CONTROL DEFINITION LANGUAGE - IN A NUTSHELL Network of Adaptive Elements - actor-like entities
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Monitoring Reconfiguration Decision Making sensors effectorsevents actions measures decisions Processor in input out output Effector in input Sensor out output Target System in input Controller in input out output Processor out output in input providedEffectorprovidedSensor out output FEEDBACK CONTROL DEFINITION LANGUAGE - IN A NUTSHELL Network of Adaptive Elements - actor-like entities
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation Goal: maintain server load around some pre-set value Prerequisite: preprocessed content (different quality and size) ILLUSTRATION
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation Goal: maintain server load around some pre-set value /1/photo.jpg /2/photo.jpg /photo.jpg full quality degraded quality Prerequisite: preprocessed content (different quality and size) ILLUSTRATION
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation Goal: maintain server load around some pre-set value /1/photo.jpg /2/photo.jpg /photo.jpg full quality degraded quality normal load overload Prerequisite: preprocessed content (different quality and size) ILLUSTRATION
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation ... serve from tree #2 serve from tree #1 Rejection Level Minimum Content Full Content Goal: maintain server load around some pre-set value /1/photo.jpg /2/photo.jpg /photo.jpg full quality degraded quality normal load overload Prerequisite: preprocessed content (different quality and size) ILLUSTRATION
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation ... serve from tree #2 serve from tree #1 Rejection Level Minimum Content Full Content Goal: maintain server load around some pre-set value /1/photo.jpg /2/photo.jpg /photo.jpg full quality degraded quality normal load overload Prerequisite: preprocessed content (different quality and size) ILLUSTRATION Distribution Complex control Generality Visibility Reusability Using FCDL
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION Compute severity of adaptation (G) Compute the requests rate (R), bandwidth (W) and utilization (U) Compute the number of requests (r) and size of responses (w)1 2 3
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION Compute the number of requests (r) and size of responses (w)1 accessLog : FileTailer out lines file=/var/log/apache2/access.log access_log active sensor FileTailer { push out port lines: String ! property file: String } processor Accumulator { push in port input: long pull out port sum: long } processor AccessLogParser { push in port lines: String push out port size: int push out port requests: int } Generality Visibility Reusability requestCounter : Accumulator responseSizeCounter : Accumulator in input out sum out sum in lines out sizeout requests accessLogParser : AccessLogParser
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION Generality Visibility Reusability access_log active processor PeriodTrigger<T> { pull in port input: T push out port output: T ! property initialPeriod = 10.seconds } requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output initialPeriod=10s accessLog : FileTailer in lines out lines file=/var/log/apache2/access_log out sizeout requests accessLogParser : AccessLogParser Compute the requests rate (R), bandwidth (W) and utilization (U)2
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION Generality Visibility Reusability content_tree access_log utilController : UtilizationController requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output in utilization out contentTree initialPeriod=10s adaptor : ContentAdaptor in contentTree accessLog : FileTailer in lines out lines file=/var/log/apache2/access_log out sizeout requests accessLogParser : AccessLogParser k=? U*=? Compute severity of adaptation (G)3
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION GeneralityVisibilityReusability composite ApacheQOS { ! feature accessLog = new FileTailer { file = “/var/log/apache2/access_log” } ! feature accessLogParser = new AccessLogParser feature requestCounter = new Accumulator feature responseSizeCounter = new Accumulator feature loadMonitor = new LoadMonitor feature scheduler = new PeriodTrigger<Double> feature utilController = new UtilizationController feature adaptor = new ContentAdaptor ! connect accessLog.lines to accessLogParser.lines connect accessLogParser.size to responseSizeCounter.input connect accessLogParser.requests to requestsCounter.input connect requestCounter.output to loadMonitor.requests connect responseSizeCounter.output to loadMonitor.size connect loadMonitor.utilization to scheduler.input connect scheduler.output to utilController.utilization connect utilController.contentTree to adaptor.contentTree } Complete model of the first prototype ApacheQOS utilController : UtilizationController in input requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output in utilization out contentTree system layer control layer initialPeriod=10s adaptor : ContentAdaptor in contentTree accessLog : FileTailer in lines out lines file=/var/log/apache2/access_log out sizeout requests accessLogParser : AccessLogParser k=? U*=?
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures COMPOSITION Generality Visibility Reusability Hierarchical organization of Adaptive Elements using composites ApacheQOS utilController : UtilizationController in input requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output in utilization out contentTree out requests out size system layer control layer composite name initialPeriod=10s adaptor : ContentAdaptor outsize in contentTree out size outrequests out requests incontentTree port promotion in contentTree ApacheWebServer server : ApacheWebServer accessLog : FileTailer accessLogParser : AccessLogParser in lines out lines file=/var/log/apache2/access_log k=? U*=? composite ApacheWebServer { ! property accessLogFile: String feature accessLog = new FileTailer { file = accessLogFile } ! feature accessLogParser = new AccessLogParser feature adaptor = new ContentAdaptor connect accessLog.lines to accessLogParser.lines ! promote accessLogParser.size promote accessLogParser.requests promote adaptor.contentTree ! }
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ApacheQOS control : QOSControl in contentTree apache : ApacheWebServer in requests in size out requests out size out contentTree control layer system layer QOSControl utilController : UtilizationController utilization : UtilizationMonitor out contentTree scheduler : PeriodTrigger out utilization in input out output in utilization out contentTreein requests in size in requests in size LighttpdQOS control : QOSControl in contentTree lighttpd : LighttpdWebServer in requests in size out requests out size out contentTree control layer system layer QOSControl utilController : UtilizationController utilization : UtilizationMonitor out contentTree scheduler : PeriodTrigger out utilization in input out output in utilization out contentTreein requests in size in requests in size COMPOSITION Generality Visibility Reusability
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures REMOTE DISTRIBUTION Remote distribution of Adaptive Elements remote-main remote-apache network ApacheQOS in contentTree in requests in size out requests out size out contentTree Apache.apache endpoint= akka.tcp://actress@remote-apache/user/Apache/apache referenced feature Apache in contentTree in requests in size out requests out size out contentTree ApacheQOS.control endpoint=akka.tcp://actress@remote-main/user/ApacheQOS/control apache: ApacheWebServer control : QOSControl composite feature // deployed at remote-apache composite Apache { feature apache = new ApacheWebServer { ... } feature control = ref ApacheQOS.control @ "akka://remote-main/user/ApacheQOS/control" } ! // deployed at host remote-main composite ApacheQOS { feature control = new QOSControl { ... } feature apache = ref Apache.apache @ "akka://remote-apache/user/Apache/apache" // ... } Distribution Visibility
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures REFLECTION Visibility ApacheQOS control layer sysLoad : SystemLoad meta-control layer periodController : PeriodController out output in load out period system layer sysLoadTrigger : PeriodTrigger in input out output in contentTree apache : ApacheWebServer in requests in size out requests out size out contentTree QOSControl scheduler : PeriodTrigger in input out output setPeriod provided in setPeriod ... ... provided effectorpromotion provided in setPeriod control : QOSControl active processor PeriodicTrigger<T> { pull in port input: T push out port output: T ! provided effector setPeriod: Long ! property initialPeriod = 10.seconds } ! composite QOSControl { // ... promote scheduler.setPeriod // ... } Complexcontrol
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Visibility Complexcontrol ApacheQOS control layer sysLoad : SystemLoad meta-control layer out output in load out period system layer in contentTree apache : ApacheWebServer in requests in size out requests out size out contentTree QOSControl scheduler : PeriodTrigger in input out output setPeriod provided in setPeriod ... ... provided effectorpromotion provided in setPeriod control : QOSControl periodControl : AdaptiveMonitoring REFLECTION - ADAPTIVE MONITORING Reusability
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures INTERACTION CONTRACTS in input : Accumulator out sum • Activated on input push request • Activated on sum pull request
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures INTERACTION CONTRACTS in input : Accumulator out sumin reset out output • Activated on input push request • Activated on reset push request • Activated on input / reset request • Activated on sum pull request • Activated on input push request always pushing data on output • Activated on reset push request always pushing data on output • ....
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures INTERACTION CONTRACTS in input : Accumulator out sumin reset out output • Behavior not explicitly stated in the architecture - Black Box • Limits verification support • Limits code-generation support When it receives data on its input port, it pushes to its output port the input value plus the sum of all the input values it has received since the last time the reset port was triggered, similarly, when pulled on the sum port, it returns the sum of all the input values since the last reset, and finally receiving any data on its reset port, sets the current accumulated value back to 0. if (!input.isEmpty()) { value += input.get output.send(value) } else if (!reset.isEmpty()) { reset.get() value = 0 } else if (!sum.isEmpty()) { sum.send(value) } else { throw new IllegalStateException("Invalid execution") }
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures INTERACTION CONTRACTS in input : Accumulator out sumin reset out output • Describe allowed interactions among components Visibility • Originally developed by Cassou et al. for SCC systems • Our extensions • Elements with multiple output ports • Multiple port connections • Composites • Composite interaction contract inference algorithm • Optional contracts • Completion verification algorithm processor Accumulator { push in port reset: int push in port input: long pull out port sum: long push out port output: long ! act onInput(input; ; output) act onSum(sum; ; ) act onReset(reset; ; ) }
28.3.2014, SAC’14 - DADSACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures The ACTRESS Modeling Environment 2
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Modeling VerificationCode Generation Tooling • Reference implementation of FCDL based on Eclipse Modeling Framework • Facilitate the use of FCDL THE ACTRESS MODELING ENVIRONMENT
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ACTRESS - MODELING SUPPORT controller UtilizationController { // ... ! // interaction contract act activate(utilization; ; contentTree) // beginning of Xbase implementation implementation xbase { var G = M ! // interaction contract act activate { // computes the error val E = targetUtilization - utilization // computes new extend of adaptation G = G + k * E ! // correct bounds if (G < 0) G = 0 if (G > M) G = M // returns the result G } } • xFCDL (Extended FCDL) • Textual DSL for authoring FCDL models • Additionally supports • Modularity • Java interoperability • Implementation specification
 using Xbase • Eclipse IDE support utilController : UtilizationController in utilization out contentTree k=? U*=?
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ACTRESS - CODE GENERATION SUPPORT accessLogParser accessLog adaptor apache control requestCounter responseSizeCounter loadMonitor utilization scheduler utilController ApacheQOS ACTRESS Runtime actor actor with event listener composite actor containment message passing ApacheQOS utilController : UtilizationController in input requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output in utilization out contentTree out requests out size initialPeriod=10s in contentTree server : ApacheWebServer k=? U*=? Code generator Model-to-Text transformation ACTRESS Domain Framework FCDL Model Executable System • Xbase compiled to Java • Skeleton implementation
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ACTRESS - CODE GENERATION SUPPORT - SKELETON IMPLEMENTATION @SuppressWarnings("all") public class UtilizationControllerAct extends AdaptiveElementAct { ! // ... ! protected double activate(final double utilization) { // TODO: compute and output value for contentTree port } ! // ... ! } utilController : UtilizationController in utilization out contentTree k=? U*=? • Prescriptive • Restrictive Visibility
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ACTRESS - VERIFICATION SUPPORT • Architecture • Consistency • Determinacy • Completeness • Interaction contracts verification @OCL(invDifferentSource="self.ports ->select(p | p.name = 'size' || p.name = 'requests') // select ports ->collect(p | p.connections) // select their connects ->collect(p | p.parent) // select owning instances ->asSet()->size() == 2 // there must be two different ones ") processor LoadMonitor { • User-defined structural constraints • xFCDL OCL annotations • User temporal constraints • FCDL to PROMELA transformation • SPIN model checker ⇤ ( accessLogParseractivate ! (⌃ utilControlleractivate)) FCDL Verification • Model well-formedness • Data-type compatibility • Port connections • Required properties • and others • Meta-model constraints
28.3.2014, SAC’14 - DADSACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Assessment and Summary 3
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ASSESSMENT • Illustration case study - running example • Additional case studies in the area of HTC computing • HTCondor Local Job Submission Overload Control • HTCondor Distributed Job Submission Overload Control c 0 1 2 1 2 Overall implementation effort Separation of concerns
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ASSESSMENT Generality Visibility Reusability • Reused elements across scenarios • Potentially any self-* property • Abstraction is close to block diagrams from control theory • Control complex schemes through reflection • FCDL is technology agnostic • xFCDL with Xbase depends on Java • ACTRESS runtime depends on Java Distribution Complex control • Case Study 2 deployed on 10 Grid5000 hosts • All case studies use hierarchical control • Eclipse based modeling environment • Model to code synthesis Tooling • Explicit FCLs • Explicit AE • Explicit AE interactions • Known concepts such as ports and composites • Higher-level of abstraction using control theory concepts
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ASSESSMENT Generality Visibility Reusability • Reused elements across scenarios • Potentially any self-* property • Abstraction is close to block diagrams from control theory • Control complex schemes through reflection • FCDL is technology agnostic • xFCDL with Xbase depends on Java • ACTRESS runtime depends on Java Distribution Complex control • Case Study 2 deployed on 10 Grid5000 hosts • All case studies use hierarchical control • Eclipse based modeling environment • Model to code synthesis Tooling • Explicit FCLs • Explicit AE • Explicit AE interactions • Known concepts such as ports and composites • Higher-level of abstraction using control theory concepts • Performance1 • ACTRESS runtime accounts for ~1.5MB • AE accounts for 400 bytes • 5000 messages accounts for 5% of CPU utilization 1 MacBook Pro 2.53 Ghz Intel i5, 8GB RAM, Java 1.70_17, Akka 2.2.0
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures SUMMARY • Combining self-adaptive software systems with principles of MDE to provide systematic and tooled approach for integrating control mechanisms into software applications. ! • A reference implementation and tools facilitating the language use including modeling, code synthesis and verification support.
Thank you Filip Křikava filip.krikava@inria.fr
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures CASE STUDIES HTCondor Client Host schedd DAGMan 1 DAGMan 2 DAGMan N User Interface Submit workflows ... Executes HTCondor cluster of worker nodes Users Spawns Submitjobs Case Study 1 Case Study 2
28.3.2014, SAC’14 - DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures CASE STUDIES HTCondor Client Host schedd DAGMan 1 DAGMan 2 DAGMan N User Interface Submit workflows ... Executes HTCondor cluster of worker nodes Users Spawns Submitjobs Case Study 1 User Interface 1 User Interface 2 User Interface N Executes HTCondor cluster of worker nodes Users Users Users Submit workflows Submit jobs ... Central schedd Case Study 2

More Related Content

PDF
PhD Thesis Defense
byFilip Krikava
 
PDF
Integrating Adaptation Mechanisms Using Control Theory Centric Architecture M...
byFilip Krikava
 
PDF
Enabling Model Testing of Cyber Physical Systems
byLionel Briand
 
KEY
On the Use of an Internal DSL for Enriching EMF Models
byFilip Krikava
 
PDF
Qualifying a high performance memory subsysten for Functional Safety
byPankaj Singh
 
PDF
Dynamic Adaptation of Software-defined Networks for IoT Systems: A Search-bas...
byLionel Briand
 
PDF
An Approach to Overcome Modeling Inaccuracies for Performance Simulation Sig...
byPankaj Singh
 
PPTX
Unified methodology for effective correlation of soc power
byPankaj Singh
 
PhD Thesis Defense
byFilip Krikava
 
Integrating Adaptation Mechanisms Using Control Theory Centric Architecture M...
byFilip Krikava
 
Enabling Model Testing of Cyber Physical Systems
byLionel Briand
 
On the Use of an Internal DSL for Enriching EMF Models
byFilip Krikava
 
Qualifying a high performance memory subsysten for Functional Safety
byPankaj Singh
 
Dynamic Adaptation of Software-defined Networks for IoT Systems: A Search-bas...
byLionel Briand
 
An Approach to Overcome Modeling Inaccuracies for Performance Simulation Sig...
byPankaj Singh
 
Unified methodology for effective correlation of soc power
byPankaj Singh
 

What's hot

PDF
Overcoming challenges of_verifying complex mixed signal designs
byPankaj Singh
 
PPTX
Jeda Hls Hlv Success Story V4
byChun Xia
 
PDF
HITECS: A UML Profile and Analysis Framework for Hardware-in-the-Loop Testing...
byLionel Briand
 
PDF
Test Case Prioritization for Acceptance Testing of Cyber Physical Systems
byLionel Briand
 
PDF
Automated Testing of Autonomous Driving Assistance Systems
byLionel Briand
 
PDF
Change Impact Analysis for Natural Language Requirements
byLionel Briand
 
PDF
Testing of Cyber-Physical Systems: Diversity-driven Strategies
byLionel Briand
 
PPTX
Detecting soft errors by a purely software approach
byMd. Hasibur Rashid
 
PDF
Automated Testing of Autonomous Driving Assistance Systems
byLionel Briand
 
PDF
Dependable Systems - Hardware Dependability with Diagnosis (13/16)
byPeter Tröger
 
PDF
Dependable Systems -Reliability Prediction (9/16)
byPeter Tröger
 
PDF
Run-time power management in cloud and containerized environments
byNECST Lab @ Politecnico di Milano
 
PDF
Combining genetic algoriths and constraint programming to support stress test...
byLionel Briand
 
PDF
Defect Prediction Over Software Life Cycle in Automotive Domain
byRAKESH RANA
 
PDF
Dependable Systems -Dependability Threats (2/16)
byPeter Tröger
 
PDF
Dependable Systems -Software Dependability (15/16)
byPeter Tröger
 
PDF
Testing the Untestable: Model Testing of Complex Software-Intensive Systems
byLionel Briand
 
PPT
Contributions to the Efficient Use of General Purpose Coprocessors: KDE as Ca...
byUnai Lopez-Novoa
 
PDF
Dependable Systems - Introduction (1/16)
byPeter Tröger
 
PDF
Dependable Systems - Structure-Based Dependabiilty Modeling (6/16)
byPeter Tröger
 
Overcoming challenges of_verifying complex mixed signal designs
byPankaj Singh
 
Jeda Hls Hlv Success Story V4
byChun Xia
 
HITECS: A UML Profile and Analysis Framework for Hardware-in-the-Loop Testing...
byLionel Briand
 
Test Case Prioritization for Acceptance Testing of Cyber Physical Systems
byLionel Briand
 
Automated Testing of Autonomous Driving Assistance Systems
byLionel Briand
 
Change Impact Analysis for Natural Language Requirements
byLionel Briand
 
Testing of Cyber-Physical Systems: Diversity-driven Strategies
byLionel Briand
 
Detecting soft errors by a purely software approach
byMd. Hasibur Rashid
 
Automated Testing of Autonomous Driving Assistance Systems
byLionel Briand
 
Dependable Systems - Hardware Dependability with Diagnosis (13/16)
byPeter Tröger
 
Dependable Systems -Reliability Prediction (9/16)
byPeter Tröger
 
Run-time power management in cloud and containerized environments
byNECST Lab @ Politecnico di Milano
 
Combining genetic algoriths and constraint programming to support stress test...
byLionel Briand
 
Defect Prediction Over Software Life Cycle in Automotive Domain
byRAKESH RANA
 
Dependable Systems -Dependability Threats (2/16)
byPeter Tröger
 
Dependable Systems -Software Dependability (15/16)
byPeter Tröger
 
Testing the Untestable: Model Testing of Complex Software-Intensive Systems
byLionel Briand
 
Contributions to the Efficient Use of General Purpose Coprocessors: KDE as Ca...
byUnai Lopez-Novoa
 
Dependable Systems - Introduction (1/16)
byPeter Tröger
 
Dependable Systems - Structure-Based Dependabiilty Modeling (6/16)
byPeter Tröger
 

Viewers also liked

PDF
Unisys Service Oriented Self Adaptive Systems
byGovCloud Network
 
PDF
Self-Adaptive Federated Authorisation Infrastructures
byLionel Montrieux
 
PDF
Model Manipulation Using Embedded DSLs in Scala
byFilip Krikava
 
PDF
A Self-Adaptive Evolutionary Negative Selection Approach for Anom
byLuis J. Gonzalez, PhD
 
PDF
Intensive Surrogate Model Exploitation in Self-adaptive Surrogate-assisted CM...
byIlya Loshchilov
 
PDF
Domain specific languages and Scala
byFilip Krikava
 
PDF
A Self-Adaptive Deployment Framework for Service-Oriented Systems
bySander van der Burg
 
PPT
Hausi Müller - Towards Self-Adaptive Software-Intensive Systems
byCHOOSE
 
PDF
Do Search-Based Approaches Improve the Design of Self-Adaptive Systems ? A Co...
bySandro Andrade
 
PDF
Architectural Design Spaces for Feedback Control in Self-Adaptive Systems Con...
bySandro Andrade
 
PPTX
Self-Adaptive SLA-Driven Capacity Management for Internet Services
byBruno Abrahao
 
PDF
201209 An Introduction to Building Affective-Driven Self-Adaptive Software
byJavier Gonzalez-Sanchez
 
PDF
Self-adaptive Systems : An Introduction
bySagar Sen
 
Unisys Service Oriented Self Adaptive Systems
byGovCloud Network
 
Self-Adaptive Federated Authorisation Infrastructures
byLionel Montrieux
 
Model Manipulation Using Embedded DSLs in Scala
byFilip Krikava
 
A Self-Adaptive Evolutionary Negative Selection Approach for Anom
byLuis J. Gonzalez, PhD
 
Intensive Surrogate Model Exploitation in Self-adaptive Surrogate-assisted CM...
byIlya Loshchilov
 
Domain specific languages and Scala
byFilip Krikava
 
A Self-Adaptive Deployment Framework for Service-Oriented Systems
bySander van der Burg
 
Hausi Müller - Towards Self-Adaptive Software-Intensive Systems
byCHOOSE
 
Do Search-Based Approaches Improve the Design of Self-Adaptive Systems ? A Co...
bySandro Andrade
 
Architectural Design Spaces for Feedback Control in Self-Adaptive Systems Con...
bySandro Andrade
 
Self-Adaptive SLA-Driven Capacity Management for Internet Services
byBruno Abrahao
 
201209 An Introduction to Building Affective-Driven Self-Adaptive Software
byJavier Gonzalez-Sanchez
 
Self-adaptive Systems : An Introduction
bySagar Sen
 

Similar to ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures

PPTX
Self Adaptive Systems
byAdeel Rasheed
 
PPTX
Self-adaptation Driven by goals in SysML Models
byamalanda1
 
PDF
Self-adaptive Software Modeling Based on Contextual Requirements
byTELKOMNIKA JOURNAL
 
PPTX
A model driven development framework for developing sense-compute-control app...
byPankesh Patel
 
PDF
09 Modeling Software Processes.pdf software
byPAKISTANSTUDIO2
 
PDF
Tackling Consistency-related Design Challenges of Distributed Data-Intensive ...
bySusanne Braun
 
PPTX
When Architecture Meets Data
byEoin Woods
 
PDF
SRCenabling application development for the internet of things
byIEI GSC
 
PDF
Towards application development for the internet of things
byPankesh Patel
 
PPTX
AI challanges - Cse day-2018.04.12
byIvica Crnkovic
 
PPTX
05 fse requirementsengineering
byMohesh Chandran
 
PDF
Quality aware approach for engineering self-adaptive software systems
bycsandit
 
ODP
Cloud accounting software uk
byArcus Universe Ltd
 
PDF
A white-box perspective on self-adaptation and self-awareness
byFET AWARE project - Self Awareness in Autonomic Systems
 
PDF
Identifying and Resolving Consistency Issues between Model Representations
byIvan Ruchkin
 
PPT
3D-DRESD AC
byMarco Santambrogio
 
PDF
A White-box Perspective on Self-Adaptation and Self-Awareness (with a focus o...
byAlberto Lluch Lafuente
 
DOCX
U. J o h n Tan i k P h .D. Apri l 2 014 SOF.docx
byouldparis
 
PDF
S-CUBE LP: Techniques for design for adaptation
byvirtual-campus
 
PDF
master_seminar
byYoussef M.Essa, MSc
 
Self Adaptive Systems
byAdeel Rasheed
 
Self-adaptation Driven by goals in SysML Models
byamalanda1
 
Self-adaptive Software Modeling Based on Contextual Requirements
byTELKOMNIKA JOURNAL
 
A model driven development framework for developing sense-compute-control app...
byPankesh Patel
 
09 Modeling Software Processes.pdf software
byPAKISTANSTUDIO2
 
Tackling Consistency-related Design Challenges of Distributed Data-Intensive ...
bySusanne Braun
 
When Architecture Meets Data
byEoin Woods
 
SRCenabling application development for the internet of things
byIEI GSC
 
Towards application development for the internet of things
byPankesh Patel
 
AI challanges - Cse day-2018.04.12
byIvica Crnkovic
 
05 fse requirementsengineering
byMohesh Chandran
 
Quality aware approach for engineering self-adaptive software systems
bycsandit
 
Cloud accounting software uk
byArcus Universe Ltd
 
A white-box perspective on self-adaptation and self-awareness
byFET AWARE project - Self Awareness in Autonomic Systems
 
Identifying and Resolving Consistency Issues between Model Representations
byIvan Ruchkin
 
3D-DRESD AC
byMarco Santambrogio
 
A White-box Perspective on Self-Adaptation and Self-Awareness (with a focus o...
byAlberto Lluch Lafuente
 
U. J o h n Tan i k P h .D. Apri l 2 014 SOF.docx
byouldparis
 
S-CUBE LP: Techniques for design for adaptation
byvirtual-campus
 
master_seminar
byYoussef M.Essa, MSc
 

Recently uploaded

PPTX
Deep Dive into Durable Functions, presented at Cloudbrew 2025
byJoonas Westlin
 
PDF
Design and Analysis of Algorithms(DAA): Unit-II Asymptotic Notations and Basi...
byKuvempu University
 
PPTX
List on Python Programming Language.pptx
byRICHARDALONSAGAY1
 
PDF
Intelligent CRM for Insurance Brokers: Managing Clients with Precision
byInsurance Tech Services
 
PPTX
Why Your Business Needs Snowflake Consulting_ From Data Silos to AI-Ready Cloud
byChetu
 
PDF
Virtual Study Circles Innovative Ways to Collaborate Online.pdf
byExplain Learning
 
PPTX
NSF Converter Software to Convert NSF to PST, EML, MSG
byNSF Converter Software
 
PDF
TNG_Architecting Green Software - An Introduction_Nils-Oliver Linden&Alexande...
byQAware GmbH
 
PDF
What Is A Woman (WIAW) Token – Smart Contract Security Audit Report by EtherA...
byEtherAuthority
 
PDF
Jeremy Millul - An NYU Computer Science Graduate
byJeremy Millul
 
PDF
nsfconvertersoftwaretoconvertNSFtoPST.pdf
byNSF Converter Software
 
PDF
How Modern Custom Software is Revolutionizing Mortgage Lending Processes -Ma...
byMatellio
 
PPTX
Binance Smart Chain Development Guide.pptx
bylakshubadai
 
PDF
Navigating SEC Regulations for Crypto Exchanges Preparing for a Compliant Fut...
byzak jasper
 
PPTX
Privacy Preserving Detection of Sensitive Data Exposure (1).pptx
byNikitaMandhan4
 
PDF
BCS-FACS Peter Landin Semantics Seminar - Formal Methods: Whence and Whither?
byJonathan Bowen
 
PDF
Manual vs Automated Accessibility Testing – What to Choose in 2025.pdf
bykalichargn70th171
 
PPTX
SNG460-CNG489_Week8_17-21Nov25_Chp8-OdtuClass.pptx
byberayseray382
 
PPTX
Modern P&C Insurance Software for Smarter, Faster Operations.pptx
byInsurance Tech Services
 
PDF
One Agent to Rule Them All - The Fellowship of AI Agents
byIvo Andreev
 
Deep Dive into Durable Functions, presented at Cloudbrew 2025
byJoonas Westlin
 
Design and Analysis of Algorithms(DAA): Unit-II Asymptotic Notations and Basi...
byKuvempu University
 
List on Python Programming Language.pptx
byRICHARDALONSAGAY1
 
Intelligent CRM for Insurance Brokers: Managing Clients with Precision
byInsurance Tech Services
 
Why Your Business Needs Snowflake Consulting_ From Data Silos to AI-Ready Cloud
byChetu
 
Virtual Study Circles Innovative Ways to Collaborate Online.pdf
byExplain Learning
 
NSF Converter Software to Convert NSF to PST, EML, MSG
byNSF Converter Software
 
TNG_Architecting Green Software - An Introduction_Nils-Oliver Linden&Alexande...
byQAware GmbH
 
What Is A Woman (WIAW) Token – Smart Contract Security Audit Report by EtherA...
byEtherAuthority
 
Jeremy Millul - An NYU Computer Science Graduate
byJeremy Millul
 
nsfconvertersoftwaretoconvertNSFtoPST.pdf
byNSF Converter Software
 
How Modern Custom Software is Revolutionizing Mortgage Lending Processes -Ma...
byMatellio
 
Binance Smart Chain Development Guide.pptx
bylakshubadai
 
Navigating SEC Regulations for Crypto Exchanges Preparing for a Compliant Fut...
byzak jasper
 
Privacy Preserving Detection of Sensitive Data Exposure (1).pptx
byNikitaMandhan4
 
BCS-FACS Peter Landin Semantics Seminar - Formal Methods: Whence and Whither?
byJonathan Bowen
 
Manual vs Automated Accessibility Testing – What to Choose in 2025.pdf
bykalichargn70th171
 
SNG460-CNG489_Week8_17-21Nov25_Chp8-OdtuClass.pptx
byberayseray382
 
Modern P&C Insurance Software for Smarter, Faster Operations.pptx
byInsurance Tech Services
 
One Agent to Rule Them All - The Fellowship of AI Agents
byIvo Andreev
 

ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures

  • 1.
    ACTRESS: Domain-Specific Modeling ofSelf-Adaptive Software Architectures SAC’14 - DADS 28.3.2014 Philippe Collet Robert B. France Colorado State University
 Computer Science Department USA Université Nice Sophia Antipolis I3S - CNRS UMR 7271
 France University Lille 1 / LIFL
 INRIA Lille
 France Filip Křikava
  • 2.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures CONTEXT Jeff Kephart - Autonomic Computing: The First Decade, ICAC’11 keynote Electronic Retailer - Application Diagram • Ever growing complexity of computing systems • Taming this complexity by skilled IT professionals does not scale • New operation modes are needed
  • 3.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures TOWARDS SELF-ADAPTIVE SOFTWARE SYSTEMS Monitoring Reconfiguration Decision Making sensors effectors Target System events actions measures decisions Feedback Control Loop (FCL) Systems that adjust themselves in accordance with some higher-level goals • response time • utilization • scheduling • concurrency policies
  • 4.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Engineering of self-adaptive software systems is a challenge Designing an adaptation engine Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ CHALLENGES
  • 5.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Engineering of self-adaptive software systems is a challenge Designing an adaptation engine Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ CHALLENGES Integrating an adaptation engine into a target system API LOGS CONFIGURATIONS COMMANDS AOP PROFILER • Consistent monitoring across all sensors • Coordination of adaptation action
  • 6.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Engineering of self-adaptive software systems is a challenge Designing an adaptation engine Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ CHALLENGES Integrating an adaptation engine into a target system API LOGS CONFIGURATIONS COMMANDS AOP PROFILER • Consistent monitoring across all sensors • Coordination of adaptation action
  • 7.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Integrating an adaptation engine into a target system Adaptation Engine Target System Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ API LOGS CONFIGURATIONS COMMANDS AOP PROFILER • Adhoc Implementations • Extensive handcrafting of non-trivial code • Cumbersome and error-prone • Accidental complexities CHALLENGES
  • 8.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Integrating an adaptation engine into a target system Adaptation Engine Target System Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ API LOGS CONFIGURATIONS COMMANDS AOP PROFILER • Reusing and adapting existing work • Often target specific types of adaptation problems [Bertran’12] • Require the use of certain adaptation mechanism [Garlan’04] • Applicable to single domain [Rouvoy’08] or technology [Asadollahi’09] • Do not support remoting or complex control schemes [Adamczyk’08, Gorton’06] • Limiting their applicability CHALLENGES
  • 9.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Derived requirements for integrating self-adaptation into software systems Generality • Domain-agnostic • Technology-agnostic • Explicit FCLs, their process and interactions • Verification support Visibility • Reusable FCL parts across adaptation scenarios Reusability • Remote distribution of FCL Distribution • Composition • Reflection Complex control • Prototyping • Automating Tooling REQUIREMENTS
  • 10.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Monitoring Reconfiguration Decision Making sensors effectors Target System events actions measures decisions Controller Target System Transduc er + - = mX i=1 1 d = m d ⇥(N) = µ = m d µ d = m (N)µ API LOGS CONFIGURATIONS COMMANDS AOP PROFILER Generality Visibility Reusability Distribution Complex control Tooling CONTRIBUTIONS Feedback Control Definition Language1 The ACTRESS Modeling Environment2 Approach facilitating systematic integration of self-adaptive mechanisms into software systems through feedback control loops.
  • 11.
    28.3.2014, SAC’14 -DADSACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures FCDL: Feedback Control Definition Language 1
  • 12.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures FEEDBACK CONTROL DEFINITION LANGUAGE 1. Raise the level of abstraction 2. Fine-grained decomposition of FCL elements 3. Explicit interactions 4. Provide reflection and composition capabilities 5. Embed remoting Monitoring Decision Making Reconfiguration measures events decisions actions General Purpose Language (GPL)Generality Visibility Reusability Distribution Complex control
  • 13.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures 1. Raise the level of abstraction 2. Fine-grained decomposition of FCL elements 3. Explicit interactions 4. Provide reflection capabilities 5. Embed remoting Domain-Specific Modeling FEEDBACK CONTROL DEFINITION LANGUAGE
  • 14.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures 1. Raise the level of abstraction 2. Fine-grained decomposition of FCL elements 3. Explicit interactions 4. Provide reflection capabilities 5. Embed remoting Domain-Specific Modeling • Feedback Control Loop • Sequence of interconnected processes • Inputs x State -> Output • Reactive • Concurrent • Dynamic Monitoring Reconfiguration Decision Making sensors effectorsevents actions measures decisions FEEDBACK CONTROL DEFINITION LANGUAGE
  • 15.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures 1. Raise the level of abstraction 2. Fine-grained decomposition of FCL elements 3. Explicit interactions 4. Provide reflection capabilities 5. Embed remoting Domain-Specific Modeling • Feedback Control Loop • Sequence of interconnected processes • Inputs x State -> Output • Reactive • Concurrent • Dynamic Monitoring Reconfiguration Decision Making sensors effectorsevents actions measures decisions • The Actor Model • Message passing actor networks • Message x State -> Message(s) • Reactive • Concurrent • Dynamic • Scalable • Remoting through location transparency actor actor actor FEEDBACK CONTROL DEFINITION LANGUAGE
  • 16.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Monitoring Reconfiguration Decision Making sensors effectorsevents actions measures decisions Processor in input out output Effector in input Sensor out output Target System in input Controller in input out output Processor out output FEEDBACK CONTROL DEFINITION LANGUAGE - IN A NUTSHELL Network of Adaptive Elements - actor-like entities
  • 17.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Monitoring Reconfiguration Decision Making sensors effectorsevents actions measures decisions Processor in input out output Effector in input Sensor out output Target System in input Controller in input out output Processor out output in input providedEffectorprovidedSensor out output FEEDBACK CONTROL DEFINITION LANGUAGE - IN A NUTSHELL Network of Adaptive Elements - actor-like entities
  • 18.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation Goal: maintain server load around some pre-set value Prerequisite: preprocessed content (different quality and size) ILLUSTRATION
  • 19.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation Goal: maintain server load around some pre-set value /1/photo.jpg /2/photo.jpg /photo.jpg full quality degraded quality Prerequisite: preprocessed content (different quality and size) ILLUSTRATION
  • 20.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation Goal: maintain server load around some pre-set value /1/photo.jpg /2/photo.jpg /photo.jpg full quality degraded quality normal load overload Prerequisite: preprocessed content (different quality and size) ILLUSTRATION
  • 21.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation ... serve from tree #2 serve from tree #1 Rejection Level Minimum Content Full Content Goal: maintain server load around some pre-set value /1/photo.jpg /2/photo.jpg /photo.jpg full quality degraded quality normal load overload Prerequisite: preprocessed content (different quality and size) ILLUSTRATION
  • 22.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Idea: service time = fixed overhead + data-size dependent overhead Abdelzaher et al., 1999, 2002 QoS management control of web servers by content delivery adaptation ... serve from tree #2 serve from tree #1 Rejection Level Minimum Content Full Content Goal: maintain server load around some pre-set value /1/photo.jpg /2/photo.jpg /photo.jpg full quality degraded quality normal load overload Prerequisite: preprocessed content (different quality and size) ILLUSTRATION Distribution Complex control Generality Visibility Reusability Using FCDL
  • 23.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION Compute severity of adaptation (G) Compute the requests rate (R), bandwidth (W) and utilization (U) Compute the number of requests (r) and size of responses (w)1 2 3
  • 24.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION Compute the number of requests (r) and size of responses (w)1 accessLog : FileTailer out lines file=/var/log/apache2/access.log access_log active sensor FileTailer { push out port lines: String ! property file: String } processor Accumulator { push in port input: long pull out port sum: long } processor AccessLogParser { push in port lines: String push out port size: int push out port requests: int } Generality Visibility Reusability requestCounter : Accumulator responseSizeCounter : Accumulator in input out sum out sum in lines out sizeout requests accessLogParser : AccessLogParser
  • 25.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION Generality Visibility Reusability access_log active processor PeriodTrigger<T> { pull in port input: T push out port output: T ! property initialPeriod = 10.seconds } requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output initialPeriod=10s accessLog : FileTailer in lines out lines file=/var/log/apache2/access_log out sizeout requests accessLogParser : AccessLogParser Compute the requests rate (R), bandwidth (W) and utilization (U)2
  • 26.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION Generality Visibility Reusability content_tree access_log utilController : UtilizationController requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output in utilization out contentTree initialPeriod=10s adaptor : ContentAdaptor in contentTree accessLog : FileTailer in lines out lines file=/var/log/apache2/access_log out sizeout requests accessLogParser : AccessLogParser k=? U*=? Compute severity of adaptation (G)3
  • 27.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ILLUSTRATION GeneralityVisibilityReusability composite ApacheQOS { ! feature accessLog = new FileTailer { file = “/var/log/apache2/access_log” } ! feature accessLogParser = new AccessLogParser feature requestCounter = new Accumulator feature responseSizeCounter = new Accumulator feature loadMonitor = new LoadMonitor feature scheduler = new PeriodTrigger<Double> feature utilController = new UtilizationController feature adaptor = new ContentAdaptor ! connect accessLog.lines to accessLogParser.lines connect accessLogParser.size to responseSizeCounter.input connect accessLogParser.requests to requestsCounter.input connect requestCounter.output to loadMonitor.requests connect responseSizeCounter.output to loadMonitor.size connect loadMonitor.utilization to scheduler.input connect scheduler.output to utilController.utilization connect utilController.contentTree to adaptor.contentTree } Complete model of the first prototype ApacheQOS utilController : UtilizationController in input requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output in utilization out contentTree system layer control layer initialPeriod=10s adaptor : ContentAdaptor in contentTree accessLog : FileTailer in lines out lines file=/var/log/apache2/access_log out sizeout requests accessLogParser : AccessLogParser k=? U*=?
  • 28.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures COMPOSITION Generality Visibility Reusability Hierarchical organization of Adaptive Elements using composites ApacheQOS utilController : UtilizationController in input requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output in utilization out contentTree out requests out size system layer control layer composite name initialPeriod=10s adaptor : ContentAdaptor outsize in contentTree out size outrequests out requests incontentTree port promotion in contentTree ApacheWebServer server : ApacheWebServer accessLog : FileTailer accessLogParser : AccessLogParser in lines out lines file=/var/log/apache2/access_log k=? U*=? composite ApacheWebServer { ! property accessLogFile: String feature accessLog = new FileTailer { file = accessLogFile } ! feature accessLogParser = new AccessLogParser feature adaptor = new ContentAdaptor connect accessLog.lines to accessLogParser.lines ! promote accessLogParser.size promote accessLogParser.requests promote adaptor.contentTree ! }
  • 29.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ApacheQOS control : QOSControl in contentTree apache : ApacheWebServer in requests in size out requests out size out contentTree control layer system layer QOSControl utilController : UtilizationController utilization : UtilizationMonitor out contentTree scheduler : PeriodTrigger out utilization in input out output in utilization out contentTreein requests in size in requests in size LighttpdQOS control : QOSControl in contentTree lighttpd : LighttpdWebServer in requests in size out requests out size out contentTree control layer system layer QOSControl utilController : UtilizationController utilization : UtilizationMonitor out contentTree scheduler : PeriodTrigger out utilization in input out output in utilization out contentTreein requests in size in requests in size COMPOSITION Generality Visibility Reusability
  • 30.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures REMOTE DISTRIBUTION Remote distribution of Adaptive Elements remote-main remote-apache network ApacheQOS in contentTree in requests in size out requests out size out contentTree Apache.apache endpoint= akka.tcp://actress@remote-apache/user/Apache/apache referenced feature Apache in contentTree in requests in size out requests out size out contentTree ApacheQOS.control endpoint=akka.tcp://actress@remote-main/user/ApacheQOS/control apache: ApacheWebServer control : QOSControl composite feature // deployed at remote-apache composite Apache { feature apache = new ApacheWebServer { ... } feature control = ref ApacheQOS.control @ "akka://remote-main/user/ApacheQOS/control" } ! // deployed at host remote-main composite ApacheQOS { feature control = new QOSControl { ... } feature apache = ref Apache.apache @ "akka://remote-apache/user/Apache/apache" // ... } Distribution Visibility
  • 31.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures REFLECTION Visibility ApacheQOS control layer sysLoad : SystemLoad meta-control layer periodController : PeriodController out output in load out period system layer sysLoadTrigger : PeriodTrigger in input out output in contentTree apache : ApacheWebServer in requests in size out requests out size out contentTree QOSControl scheduler : PeriodTrigger in input out output setPeriod provided in setPeriod ... ... provided effectorpromotion provided in setPeriod control : QOSControl active processor PeriodicTrigger<T> { pull in port input: T push out port output: T ! provided effector setPeriod: Long ! property initialPeriod = 10.seconds } ! composite QOSControl { // ... promote scheduler.setPeriod // ... } Complexcontrol
  • 32.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Visibility Complexcontrol ApacheQOS control layer sysLoad : SystemLoad meta-control layer out output in load out period system layer in contentTree apache : ApacheWebServer in requests in size out requests out size out contentTree QOSControl scheduler : PeriodTrigger in input out output setPeriod provided in setPeriod ... ... provided effectorpromotion provided in setPeriod control : QOSControl periodControl : AdaptiveMonitoring REFLECTION - ADAPTIVE MONITORING Reusability
  • 33.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures INTERACTION CONTRACTS in input : Accumulator out sum • Activated on input push request • Activated on sum pull request
  • 34.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures INTERACTION CONTRACTS in input : Accumulator out sumin reset out output • Activated on input push request • Activated on reset push request • Activated on input / reset request • Activated on sum pull request • Activated on input push request always pushing data on output • Activated on reset push request always pushing data on output • ....
  • 35.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures INTERACTION CONTRACTS in input : Accumulator out sumin reset out output • Behavior not explicitly stated in the architecture - Black Box • Limits verification support • Limits code-generation support When it receives data on its input port, it pushes to its output port the input value plus the sum of all the input values it has received since the last time the reset port was triggered, similarly, when pulled on the sum port, it returns the sum of all the input values since the last reset, and finally receiving any data on its reset port, sets the current accumulated value back to 0. if (!input.isEmpty()) { value += input.get output.send(value) } else if (!reset.isEmpty()) { reset.get() value = 0 } else if (!sum.isEmpty()) { sum.send(value) } else { throw new IllegalStateException("Invalid execution") }
  • 36.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures INTERACTION CONTRACTS in input : Accumulator out sumin reset out output • Describe allowed interactions among components Visibility • Originally developed by Cassou et al. for SCC systems • Our extensions • Elements with multiple output ports • Multiple port connections • Composites • Composite interaction contract inference algorithm • Optional contracts • Completion verification algorithm processor Accumulator { push in port reset: int push in port input: long pull out port sum: long push out port output: long ! act onInput(input; ; output) act onSum(sum; ; ) act onReset(reset; ; ) }
  • 37.
    28.3.2014, SAC’14 -DADSACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures The ACTRESS Modeling Environment 2
  • 38.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Modeling VerificationCode Generation Tooling • Reference implementation of FCDL based on Eclipse Modeling Framework • Facilitate the use of FCDL THE ACTRESS MODELING ENVIRONMENT
  • 39.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ACTRESS - MODELING SUPPORT controller UtilizationController { // ... ! // interaction contract act activate(utilization; ; contentTree) // beginning of Xbase implementation implementation xbase { var G = M ! // interaction contract act activate { // computes the error val E = targetUtilization - utilization // computes new extend of adaptation G = G + k * E ! // correct bounds if (G < 0) G = 0 if (G > M) G = M // returns the result G } } • xFCDL (Extended FCDL) • Textual DSL for authoring FCDL models • Additionally supports • Modularity • Java interoperability • Implementation specification
 using Xbase • Eclipse IDE support utilController : UtilizationController in utilization out contentTree k=? U*=?
  • 40.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ACTRESS - CODE GENERATION SUPPORT accessLogParser accessLog adaptor apache control requestCounter responseSizeCounter loadMonitor utilization scheduler utilController ApacheQOS ACTRESS Runtime actor actor with event listener composite actor containment message passing ApacheQOS utilController : UtilizationController in input requestCounter : Accumulator responseSizeCounter : Accumulator scheduler : PeriodTrigger loadMonitor : LoadMonitor in input out sum out sum in requests in size out utilization in input out output in utilization out contentTree out requests out size initialPeriod=10s in contentTree server : ApacheWebServer k=? U*=? Code generator Model-to-Text transformation ACTRESS Domain Framework FCDL Model Executable System • Xbase compiled to Java • Skeleton implementation
  • 41.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ACTRESS - CODE GENERATION SUPPORT - SKELETON IMPLEMENTATION @SuppressWarnings("all") public class UtilizationControllerAct extends AdaptiveElementAct { ! // ... ! protected double activate(final double utilization) { // TODO: compute and output value for contentTree port } ! // ... ! } utilController : UtilizationController in utilization out contentTree k=? U*=? • Prescriptive • Restrictive Visibility
  • 42.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ACTRESS - VERIFICATION SUPPORT • Architecture • Consistency • Determinacy • Completeness • Interaction contracts verification @OCL(invDifferentSource="self.ports ->select(p | p.name = 'size' || p.name = 'requests') // select ports ->collect(p | p.connections) // select their connects ->collect(p | p.parent) // select owning instances ->asSet()->size() == 2 // there must be two different ones ") processor LoadMonitor { • User-defined structural constraints • xFCDL OCL annotations • User temporal constraints • FCDL to PROMELA transformation • SPIN model checker ⇤ ( accessLogParseractivate ! (⌃ utilControlleractivate)) FCDL Verification • Model well-formedness • Data-type compatibility • Port connections • Required properties • and others • Meta-model constraints
  • 43.
    28.3.2014, SAC’14 -DADSACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures Assessment and Summary 3
  • 44.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ASSESSMENT • Illustration case study - running example • Additional case studies in the area of HTC computing • HTCondor Local Job Submission Overload Control • HTCondor Distributed Job Submission Overload Control c 0 1 2 1 2 Overall implementation effort Separation of concerns
  • 45.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ASSESSMENT Generality Visibility Reusability • Reused elements across scenarios • Potentially any self-* property • Abstraction is close to block diagrams from control theory • Control complex schemes through reflection • FCDL is technology agnostic • xFCDL with Xbase depends on Java • ACTRESS runtime depends on Java Distribution Complex control • Case Study 2 deployed on 10 Grid5000 hosts • All case studies use hierarchical control • Eclipse based modeling environment • Model to code synthesis Tooling • Explicit FCLs • Explicit AE • Explicit AE interactions • Known concepts such as ports and composites • Higher-level of abstraction using control theory concepts
  • 46.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures ASSESSMENT Generality Visibility Reusability • Reused elements across scenarios • Potentially any self-* property • Abstraction is close to block diagrams from control theory • Control complex schemes through reflection • FCDL is technology agnostic • xFCDL with Xbase depends on Java • ACTRESS runtime depends on Java Distribution Complex control • Case Study 2 deployed on 10 Grid5000 hosts • All case studies use hierarchical control • Eclipse based modeling environment • Model to code synthesis Tooling • Explicit FCLs • Explicit AE • Explicit AE interactions • Known concepts such as ports and composites • Higher-level of abstraction using control theory concepts • Performance1 • ACTRESS runtime accounts for ~1.5MB • AE accounts for 400 bytes • 5000 messages accounts for 5% of CPU utilization 1 MacBook Pro 2.53 Ghz Intel i5, 8GB RAM, Java 1.70_17, Akka 2.2.0
  • 47.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures SUMMARY • Combining self-adaptive software systems with principles of MDE to provide systematic and tooled approach for integrating control mechanisms into software applications. ! • A reference implementation and tools facilitating the language use including modeling, code synthesis and verification support.
  • 48.
  • 49.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures CASE STUDIES HTCondor Client Host schedd DAGMan 1 DAGMan 2 DAGMan N User Interface Submit workflows ... Executes HTCondor cluster of worker nodes Users Spawns Submitjobs Case Study 1 Case Study 2
  • 50.
    28.3.2014, SAC’14 -DADS ACTRESS: Domain-Specific Modeling of Self-Adaptive Software Architectures CASE STUDIES HTCondor Client Host schedd DAGMan 1 DAGMan 2 DAGMan N User Interface Submit workflows ... Executes HTCondor cluster of worker nodes Users Spawns Submitjobs Case Study 1 User Interface 1 User Interface 2 User Interface N Executes HTCondor cluster of worker nodes Users Users Users Submit workflows Submit jobs ... Central schedd Case Study 2