15.12.2012 Views

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

deploying and managing ip over wdm networks - Index of

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The WINMAN Management System Concept 105<br />

• Activate policies UC. The purpose <strong>of</strong> activating policies at the user level<br />

is to instantiate a certain set <strong>of</strong> policies in the appropriate system components,<br />

leaving it ready to be used by the execute policies UC.<br />

• Execute policies UC. The purpose <strong>of</strong> execute policies at the user level is<br />

to carry out actions according to an instantiated policy. The policy conditions<br />

are checked <strong>and</strong> the relevant actions are executed. This UC may<br />

be called from any <strong>of</strong> the NP, NIM, NM&R, <strong>and</strong> NDM UCs.<br />

• Check policy UC. The check policy at the atomic level is intended to<br />

determine both the policy validity in itself <strong>and</strong> whether it is in conflict<br />

with all other existing policies. The princ<strong>ip</strong>al mechanisms driving this<br />

check will be dictated by rules specifically designed for such a purpose.<br />

These rules are called metapolicies.<br />

• Find policy UC. The purpose <strong>of</strong> this UC at atomic level is to find a<br />

given policy in the repository.<br />

6.4.2.2 Scheduling<br />

The scheduler is a part <strong>of</strong> functionality in the WINMAN system to perform a<br />

variety <strong>of</strong> tasks on such areas as (but not limited to):<br />

• Connection management (implementing/activating a network connection);<br />

• Configuration management (periodically making changes in the network);<br />

• Fault management (providing fault management summary reports once<br />

or on a certain time base, or changing correlation rules);<br />

• Performance management (providing time-based reports or changing<br />

thresholds);<br />

• System administration (performing backups);<br />

• Policy management (executing policies).<br />

The scheduler keeps a list <strong>of</strong> tasks to be scheduled. These tasks are in princ<strong>ip</strong>le<br />

performed in a chronological fashion but also take into account the task<br />

priority. However, policies that apply to the scheduler can <strong>over</strong>ride the execution<br />

order.<br />

The task to be scheduled can have a fixed date <strong>and</strong> time but can also have a<br />

periodical schedule. The task owner is entitled to request the scheduling <strong>of</strong> a<br />

task. Two possible owners are distinguished; a task is owned either by the<br />

WINMAN operator or by the connection management UCs (provide<br />

ICS/delete ICS/modify ICS).<br />

• Schedule task UC. A task is added to the task list <strong>of</strong> the scheduler.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!