cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
88
Views
0
Helpful
3
Replies
khgrant
Cisco Employee

NFVO package and ESC KPI parameters

 

Hi Team,

 

 

Using NFVO 1.3 and have found with the new ESC 2.3 updated timers that for some VDUs we need to change the KPI polling frequency and/or number of retries to accommodate failover or bootup requirements. We have noticed these values are not bubbled up into the YANG model but hard coded in the ESC template.

 

 

Thus when we change these values it changes for ALL VDUs! Will NFVO 2.0 have these values as yang inputs? Or do we need to open a TAC Case/RT for this?

 

 

 

Tailf-nfvo-esc-mgmt-interface.xml:

 

 

<config-template xmlns="http://tail-f.com/ns/config/1.0">

 

  <devices xmlns="http://tail-f.com/ns/ncs">

 

    <device tags="nocreate">

 

      <name>{/esc}</name>

 

      <config>

 

        <esc_datamodel xmlns="http://www.cisco.com/esc/esc">

 

          <tenants>

 

            <tenant>

 

              <name>{/tenant}</name>

 

              <deployments>

 

                <deployment>

 

                  <name>{/deployment-name}</name>

 

                  <vm_group tags="merge">

 

                    <name>{$VDU}</name>

 

                    <kpi_data>

 

                      <kpi>

 

                        <event_name>VM_ALIVE</event_name>

 

                        <metric_value>1</metric_value>

 

                        <metric_cond>GT</metric_cond>

 

                        <metric_type>UINT32</metric_type>

 

                        <metric_occurrences_true>1</metric_occurrences_true>

 

                        <metric_occurrences_false>10</metric_occurrences_false>

 

                        <metric_collector>

 

                          <nicid>{$NICID}</nicid>

 

                          <type>{$KPI-METER-TYPE}</type>

 

                          <poll_frequency>30</poll_frequency>

 

                          <polling_unit>seconds</polling_unit>

 

                          <continuous_alarm>false</continuous_alarm>

 

                        </metric_collector>

 

                      </kpi>

 

                    </kpi_data>

 

 

 

Thanks, JA

 

3 REPLIES 3
khgrant
Cisco Employee

 

Hello JA,

 

 

You can change kpi_data using  such as following esc device template. NFVO write device template data on existing data. Because kpi_data is identified by event_name, Data with same event_name is merged it.

 

---

 

<config xmlns="http://tail-f.com/ns/config/1.0">

 

  <devices xmlns="http://tail-f.com/ns/ncs">

 

  <template>

 

    <name>my-kpi-data</name>

 

    <config>

 

      <esc_datamodel xmlns="http://www.cisco.com/esc/esc">

 

        <tenants>

 

          <tenant>

 

            <name>{$TENANT}</name>

 

            <deployments>

 

              <deployment>

 

                <name>{$DEPLOYMENT_NAME}</name>

 

                  <vm_group>

 

                  <name>{$VDU}</name>

 

                  <kpi_data>

 

                      <kpi>

 

                        <event_name>VM_ALIVE</event_name>

 

                        <metric_value>1</metric_value>

 

                        <metric_cond>GT</metric_cond>

 

                        <metric_type>UINT32</metric_type>

 

                        <metric_occurrences_true>1</metric_occurrences_true>

 

                        <metric_occurrences_false>10</metric_occurrences_false>

 

                        <metric_collector>

 

                          <nicid>{$NICID}</nicid>

 

                          <type>{$KPI-METER-TYPE}</type>

 

                          <poll_frequency>30</poll_frequency>

 

                          <polling_unit>seconds</polling_unit>

 

                          <continuous_alarm>false</continuous_alarm>

 

                        </metric_collector>

 

                      </kpi>

 

                  </kpi_data>

 

                  </vm_group>

 

              </deployment>

 

            </deployments>

 

          </tenant>

 

        </tenants>

 

      </esc_datamodel>

 

    </config>

 

  </template>

 

  </devices>

 

</config>

 

----

 

 

For more information, see "Setting additional parameters using device templates" in nfvo.pdf.

 

 

Best regards,

 

Yoshitaka Nagami

 

khgrant
Cisco Employee

 

Yoshitaka,

 

 

So I believe you are implying to need to use an ESC template during deployment – will this override the template already called by the NFVO code as cited below?

 

 

We use templates for other items so I am familiar with how to do that. But usually we use them when NFVO templates do not support a given ESC feature.

 

 

Thanks,

JA

 

khgrant
Cisco Employee

 

Hi JA,

 

 

> will this override the template already called by the NFVO code as cited below?

 

Yes, because NFVO apply esc-device-tamplate after all NFVO's templates loaded, you can not only add support feature but also overwrite parameters configured by NFVO.

 

Because kpi_data is identified by event_name, Data with same event_name is merged it. Of course, if you use different event_name, kpi_data is added.

 

 

Best regards,

 

Yoshitaka Nagami

 

Content for Community-Ad

This widget could not be displayed.