You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The Policy Creation subsystem provides a centralized environment for  the creation and management of easily-updatable conditional rules. This subsystem enables users to validate policies and rules, identify and resolve overlaps & conflicts, and derive additional policies where needed. You access the Policy Creation subsystem from the OpenECOMP Portal.

Policies are used to control, to influence, and to help ensure compliance with goals. A policy can be defined at a high level to create a condition, requirement, constraint, or need that must be provided, maintained, and enforced. A policy can also be defined at a lower or functional level, such as a machine-readable rule or software condition/assertion which enables actions to be taken based on a trigger or request, specific to particular selected conditions in effect at that time.   Software policies that are supported include XACML policies, Drool policies, and lower level policies that are embodied in models such as YANG and TOSCA.

Policies can support infrastructure, products and services, operation automation, and security. Various stakeholders such as network and service designers, operations engineers, and security experts can use the Policy Creation subsystem to support their goals.

The Policy Creation subsystem also provides additional functionality once policies are initially created:

  • Offline analysis of performance, fault, and closed-loop actions, enabling the discovery of new and signatures and refinement of existing ones
  • Derivation of lower-level policies from higher-level policies
  • Identification of conflicts and mitigation of them before deployment

Once validated and free of conflicts, policies are placed in an appropriate repository.

  • No labels