Subject: [Supa] VPN model statets and parameters

From: Maxim Klyus <[email-masked]>
Date: Tue, 28 Apr 2015 12:54:15 +0000

Hello L3SM and SUPA,

Finally I decided to align all my proposal terminology and states to ITU-T (except Administrative State, because context a little bit different).

http://www.itu.int/rec/T-REC-X.731/en

rw - read/write
ro - read only

Administrative State (RW) - administrative decision service enabling/disabling

Enabled - service administratively enabled, service configuration structure unchanged, but service component states can be changed)
Disabled - service administratively disabled, service configuration structure unchanged, but service component states can be changed)

Operational State (RO) - Service operational state indicate current service state

Enabled - service is enabled and can operate normally or with some errors
Disabled - service disabled administratively or automatically based on some critical errors

Life Cycle State (RW) - Service Life Cycle Management and Configuration

Planned - service planed, service configuration prepared, resources temporary allocated and reserved
Installed - service managed, service configuration applied to service components, resources allocated and reserved
Removed - service removed, configuration removed from the service components and saved for history and resources are free now

Availability Status (RO) - Service availability status (health status) based on this parameter we can say if Operational State will be Enabled or Disabled

Degraded - service administratively enabled (Operational State = Enabled), but some of the service components have an errors.
Failed - service disabled based on SLA policy (Operational State = Disabled), because some of the service components have too many errors.

Actually "Availability Status" accordingly to ITU-T have many other states I'm not sure if need include all of them.

Science service configuration could be modified (expanded/reduced) - VPN instance will be unchanged but service components can be changed it will be useful to add Revision parameter.
Based on this parameter we can track configuration changes history and indicate last active configuration.

"Service Configuration Revision" - track service configuration changes.

Decision about operational service state can be very complicated it will be useful to add SLA Decision policy - parameter and do not add any states to VPN components.
Based on this parameter SP can implement some SLA decision policy per VPN service basis.

"SLA Decision Policy" - reference to SLA policy (set of specific rules and conditions) Service Operational State - Enabled / Disabled

Best Regards,
Maxim Klyus

________________________________
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.