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 5 Next »

To disable CPS-temporal notifications we need to have following properties configured as below :

Property

Description

Path from CPS root

NOTIFICATION_DATASPACE_FILTER_PATTERNS: NON-EXISTING-DATASPACE
  • Add / modify under services.cps-and-ncmp.environment section
docker-compose/docker-compose.yml
notification.enabled: 'true'
  • Add / modify under services.cps-and-ncmp.environment section.
  • Make sure to always enable it as it is used by CPS for Async/Internal communications.
docker-compose/docker-compose.yml

docker-compose.yml view : 

docker-compose (cps-and-ncmp) 
cps-and-ncmp:
  container_name: cps-and-ncmp
  image: ${DOCKER_REPO:-nexus3.onap.org:10003}/onap/cps-and-ncmp:${CPS_VERSION:-latest}
  ports:
    - ${CPS_CORE_PORT:-8883}:8080
    - ${CPS_CORE_MANAGEMENT_PORT:-8887}:8081
  environment:
    notification.enabled: 'true'
    NOTIFICATION_DATASPACE_FILTER_PATTERNS: NON-EXISTING-DATASPACE

To verify if CPS-temporal notifications are disable :

Add consumer docker-compose service for topic  "cps.data-updated-events" as below : 

docker-compose (kafka-consumer) 
  consumer:
    image: taion809/kafka-cli:latest
    container_name: kafka-consumer
    command: kafka-console-consumer.sh --bootstrap-server kafka:9092 --topic cps.data-updated-events
    links:
      - kafka

Open kafka-consumer "Logs" section as below :

If CPS-temporal notifications are disabled will see warning message as "WARN [Consumer clientId=consumer-1, groupId=console-consumer-32597] Error while fetching metadata with correlation id 9 : {cps.data-updated-events=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)" else

CM handle notifications  :

  • No labels