Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 3 Current »

 Why Policy Driven Naming

Why Policy Driven Naming 

  • Naming conventions can change and will change! Policy driven naming separates the ever changing data set (naming recipes, naming element usage, sequence # definitions, etc.) from the relatively stable processing mechanism (ingredient assembly, element processing mechanism, etc.)
  • Dynamic data are kept in policy instances while processing mechanism is maintained standalone in the name mS
  • Policy (Data) driven naming solution enhance maintainability and overall turn around time for development; ultimately empowers end user, providing means to make fine adjustment to Naming recipes in policy instance without trigger code churns.
 Policy Driven Solution Strategy – Creation to Execution

Policy Driven Solution Strategy – Creation to Execution

 Work Flows

 Sample Naming Parameters To be Policy Driven

Sample Naming Parameters To be Policy Driven


Parameter Type

Cloud Param name

Proposed Recipe

New

Current

vnf-name

${vnf-name}

${aic-cloud-region}+”_”+${nf_role} +”_”+Timestamp

e.g. region = ATL03 (input) & nf_role = vfw (input)

ATL03_vFW_20181012T190639982Z

Vfmodule_Ete_vFWSNK_ceeabd15-8970-4713-91e9-86ae18284cd7

vnfc-name

${vsn_name_0}

${vfw_name_0}

${vpg_name_0}

${vlb_name_0}

${vdns_name_0}

${scaling_vdns_name_0}

${vnf-name} +”_”+ ${nfc_naming_code}+”_”+index#

E.g. Index # = 3 char alpha-numeric

(001 … 009, 00a, … 00z, 010 … zzz)

ATL03_vFW_20181012T190639982Z

_vsn_001

ATL03_vFW_20181012T190639982Z

_vfw_001

Vofwl01snk4cd7

Vofwl01fwl4cd7


Vf-module-name


???

${vnf-name} + “_” + ${vf_module_label} + “_” + ${vf_module_type} + “_” + index#

E.g. Index # = 3 char alpha-numeric

(001 … 009, 00a, … 00z, 010 … zzz)

ATL03_vFW_20181012T190639982Z

_SAMPLELABEL_SAMPLEMODULETYPE_001


key_name

${key_name}


Vnf name

ATL03_vFW_20181012T190639982Z

vfw_keyceeabd15-8970-4713-91e9-86ae18284cd7

protected_private_net_id

${protected_private_net_id}

${vnf-name} + “protected”

ATL03_vFW_20181012T190639982Z

_protected

vofwlsnk_protected4cd7

Unprotected_private_net_id

${unprotected_private_net_id}

${vnf-name} + “unprotected”

ATL03_vFW_20181012T190639982Z

_unprotected

vofwlsnk_unprotected4cd7



 Sample Policy - vFW (Policy Manager generated JSON)

Sample Policy – vFW (PM Generated JSON)


 Beyond Policy Driven Naming

Beyond Naming

 ONAP Naming Policies - vFW, vSN & vPG

Policy Export for vFW, vSN & vPG

Naming Model

  • This is the .yml file to be ingested by Policy Manager to allow policy creation - DO NOT modify

  • No labels