Uploaded image for project: 'Test'
  1. Test
  2. TEST-168

[vFWCL] Policy ControlLoop name is not matching with TCA

    Details

      Description

      This is known deficiency described in DOC

      https://docs.onap.org/en/dublin/submodules/integration.git/docs/docs_vfw.html

       

      The control loop name in DCAE’s TCA micro-service needs to match the Operational Policy control loop name. Due to timing robot scripts that setup the operational policy do not change the control loop name in DCAE. Do the following to update DCAE’s consul entry for TCA to match the name assigned by robot to the operational policy. The control loop name generated by policy can be viewed in the log.html page on robot from the instantiateVFWCL.

      • Connect to Consul: http://<k8s_host_ip>:30270/ui/#/dc1/services (change the IP based on the K8S cluster IP assignment)
      • Click Key/Value on the bar at the top of the Consul menu
      • Select “dcae-tca-analytics” microservice from the list on the left
      • Search for “closedLoopControlName” key in the configuration policy JSON object
      • Replace the standard ControlLoop-vFirewall-* closed loop names with the one generated by robot
      • Click “Update” button to update the configuration policy

       

      the aim of this task is to fix this part to make instantiateVFWCL working E2E

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              Michal.Ptacek Michal Ptacek
              Reporter:
              Michal.Ptacek Michal Ptacek
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: