Cisco Elastic Services Controller 5.2 User Guide

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Elastic Services Controller 5.2 User Guide

Chapter Title

Policy-Driven Data Model

Results

Updated:
May 31, 2020

Chapter: Policy-Driven Data Model

Policy-Driven Data Model

Policy-Driven Data model

ESC supports a new policy-driven datamodel. A new <policy> section is introduced under <policies> at both deployment and VM group level.

Using the policy-driven datamodel, a user can perform actions based on conditions. ESC supports predefined actions, or customized scripts during a deployment based on certain Lifecycle Stage (LCS). For example, the redeployment policy uses predefined actions based on lifecycle stages (LCS) to redeploy VMs. For more information, see Redeployment Policy.

Policy Data model

The policy data model consists of conditions and actions. The condition is a Lifecycle Stage (LCS) in a deployment. The action is predefined or custom script.

  • Predefined action—The action is predefined and executed when the condition is met.

    In the datamodel below, when condition2 is met, Action2 is performed. The action <type> is predefined.

  • Custom Script—The action is a custom script, and executed when the condition is met.

    In the datamodel below, when condition1 is met, Action1-1 and Action 1-2 are executed. The action <type> is script. 
    <policies>
    <policy>
        <name>Name1</name>
        <conditions>
            <condition>
                <name>Condition1</name>
            </condition>
        </conditions>
        <actions>
            <action>
                <name>Action1-1</name>
                <type>SCRIPT</type>
            </action>
            <action>
                <name>Action1-2</name>
                <type>SCRIPT</type>
            </action>
        </actions>
    </policy>
    <policy>
        <name>Name2</name>
        <conditions>
            <condition>
                <name>Condition2</name>
            </condition>
        </conditions>
        <actions>
            <action>
                <name>Action2</name>
                <type>PRE-DEFINED</type>
            </action>
        </actions>
    </policy>
</policies>

For more information on Predefined actions, and scripts, see Recovery and Redeployment Policies.

The table below shows the LCS in a deployment, and its description. The recovery and redeployment policies, and VNF software upgrade policies use the policy-driven data model. These policies are supported on both single deployment and multi VIM deployment. For more information, see "Deploying Virtual Network Functions". For details on configuring the recovery and redeployment policies using the policy framework, see Recovery and Redeployment Policies. For details on upgrading the VNF software upgrade policies, see Upgrading VNF Software with Volume.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco