Infrastructure & Methodology

(The cool group)

Problem space• What is “self-management” anyway?

– Defined broadly - anything that does not require (or reduces) human interaction after configuration or indication of intention

• Insight: service level differs from device level• Consequence: Human intention specified at

service level– Translated to device level– Control loop handles issues when intention is not met

Yet more problem space

• Two separate infrastructures are required– One that accommodates the new self-management tools

and methods (the real system)– One for measurement & evaluation testing (the control

plane)

• Models (abstractions) for configuration and workload are required for simulation and emulation– The evaluation environment must provide level of

detail appropriate to self-management system/method being considered

Requirements

• Managed require extended capabilities– Ability to express formal specification of intent

• Extended UPNP?

– Ability to express capability– Ability to express current status

• Put into a model and a basis for control action

Next steps

• How do we make progress?– Establish a baseline for self-management– Establish metrics and measurement

methods/tools for evaluating self-management– Establish evaluation infrastructures (simulation,

emulation, in-situ)

Research opportunities

• Network configuration (service level) specification– Optimize performance (sla’s) for minimum cost

• Best practices for translating to service policies given device capabilities

• Understand device/protocol interactions• Define and collect metrics for improvement

– Down time/failures– Volume of help desk complaints– Human involvement– Simplicity(?)

Opportunities continued

• Build “Controllers” for self-management components

• Define testbeds (simulation, emulation, in situ)– Instrumentation to evaluate and validate– Test cases– Simulation models