1 / 11

Analyzing Security and Energy Tradeoffs in Autonomic Capacity Management

Analyzing Security and Energy Tradeoffs in Autonomic Capacity Management. Wei Wu. Introduction. Capacity management of hosting infrastructure Achieve performance goal traditionally QoS and the revenues impact of security attacks energy cost and constraints Cost effective solution

callum
Download Presentation

Analyzing Security and Energy Tradeoffs in Autonomic Capacity Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Analyzing Security and Energy Tradeoffs in Autonomic Capacity Management Wei Wu

  2. Introduction • Capacity management of hosting infrastructure • Achieve performance goal traditionally • QoS and the revenues • impact of security attacks • energy cost and constraints • Cost effective solution • Previous strategies: performance issue • Self-adaptive capacity management framework: dynamically allocates capacity among applications so as to maximize the provider’s revenues • a pricing model • Service Level Agreement (SLA) contracts • a queuing-based performance model • an optimization model • Energy-related costs • Previous works • simplified assumptions of single-tier platforms or guarantees only on average performance targets • addressing security issues aim at improving robustness, and are disconnected from the capacity management goal • Main goals: to build cost-effective framework to address jointly three issues that are key to capacity management

  3. Background • Autonomic Capacity Management for Multi-Tier Services • The case of a provider hosting third-party applications on a shared infrastructure • The customers, sign Service Level Agreement (SLA) contracts with the provider • Each hosted application may be composed of multiple request types: application class, the provider hosts N classes • The shared platform is composed of K tiers • After being served at tier j, a class i request leaves the system with probability pi,j (i = 1..N, j = 1..K, pi,K = 1) or enters tier j + 1. • The capacity allocation problem • the determination of the fraction of the physical capacity of each tier j to each class i that maximizes the provider’s business goal • Self-adaptive capacity management framework

  4. Autonomic Capacity Management for Multi-Tier Services: Pricing Model • The pricing model specifies QoS requirements and hosting costs, thus, captures the SLA contracts • Normal • the valid throughput that is expected to satisfy class i requirements most of the time • In case of SLA violations, the provider must refund the customer cifor each unit of throughput below • Surge • the maximum valid throughput up to which the customer agrees to pay extra (ri per unit of valid throughput above ) to accommodate occasional load peaks • The valid throughput includes all accepted requests served with a response time that satisfies the SLA • the system response time experienced by each class i request, Ri, exceeds threshold , that is, • Given λi, class i request arrival rate, and , the rate of requests accepted into the system, computed by the capacity manager, the provider’s revenues from class i, gi,

  5. Autonomic Capacity Management for Multi-Tier Services: Performance Model • The analytical queuing-based performance model estimates, system throughput and the probability of system response time SLA violations • the average service time of a class i request running on tier j’s full capacity • The average service time of a class i request at its assigned VM on tier j, di,j , is then computed as di,j = / fi,j • Assumptions • For each hosted class i, the model assumes Poisson request arrivals with rate λi, as observed in real systems, and exponentially distributed service times at each tier j, with average di,j • Each VM is modeled as an M/M/1 queue with FCFS scheduling discipline • The probability that a class i request violates its system response time SLA, , can be derived from the distribution of system response time Ri

  6. Autonomic Capacity Management for Multi-Tier Services: Optimization Model • The pricing and performance models are combined into an optimization model with an objective function that expresses the provider’s goal of maximizing total revenues • Constraints are added to specify limits • the accepted request rates • per-tier allocated capacity • VM utilizations • effective request rates • express the SLA tail distribution response time requirement for each class

  7. Capacity Management under Security Attacks and Energy Constraints • Goals • Uncover primary tradeoffs in managing capacity of a shared infrastructure under security attacks and energy constraints • Evaluate the cost-effectiveness of adaptive SLA contracts. • Security Attacks • A flooding of illegitimate requests • even though they might be detected, illegitimate requests can not be individually blocked before being processed, as they look like legitimate ones • , plus means the rate of legitimate requests, minus means the rate of illegitimate requests • the service of a fraction of class i legitimate requests implies extra costs to the provider, as some of the illegitimate requests will also be admitted into the system, consuming resources • the provider’s revenues from class i, computed only over its goodput

  8. Solutions built from variants of Baseline framework: Security Attacks • Attack-Oblivious (AO) • the provider is unaware that class i is under attack • Capacity management is done using our original framework, which relies on estimates of revenues given by Equation 1, however actually, by using Equation 2 • Attack-Aware (AA) • using the extended framework • Two other strategies based on adaptive SLA contracts • victim customer may agree to either pay extra for each legitimate request served within the pre-defined SLA, or, for fixed costs, relax the response time target • Adaptive Cost (AC) • agree to pay an amount for each legitimate request served that is inflated by the attack weight • Adaptive (S-AR) • agree to relax by a factor proportional to the attack weight

  9. Solutions built from variants of Baseline framework: Energy Constraints • Goal • uncover primary tradeoffs in managing capacity of a shared infrastructure under security attacks and energy constraints • The original expression for revenues is • ej is the cost per time unit of operation of tier j at its full capacity • energy constrains,where C is the total available capacity and constants sjare used to normalize tier capacities • Solutions • Energy-Oblivious (EO) • using the original framework, which does not capture energy costs • Energy-Aware (EA) • using the extended framework with the aforementioned changes • Adaptive (E-AR) • the owner of application class i may agree to relax its response time SLA by a factor proportional to S to achieve higher throughput under the reduced allocation, where S is a fraction reduced of energy consumed by the infrastructure

  10. Conclusion • This paper extends the capacity management framework to capture key cost and performance tradeoffs introduced by security attacks and energy constraints • Contributions • introducing energy and security awareness into our framework provides great revenue gains at the cost of goodput degradation, particularly for applications under attacks or with heavy demands on the costlier tiers • dynamic SLA strategies can help reduce goodput degradation • response time SLA relaxation also reduces degradation due to an attack or energy constraint, although its benefit depends on the original SLA, on the relaxation factor and on target utilizations • Future work • the design of more sophisticated models of energy costs and security attacks • extensions to take the end-user perspective into the design of service reputation, workload forecasting and request prioritization mechanisms

  11. Thank you! Questions?

More Related