Versions Compared

Old Version 83

changes.mady.by.user David Perez Caparros

Saved on

compared with

New Version Current

changes.mady.by.user David Perez Caparros

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagebash
themeMidnight
titleunauthenticated.PNF_UPDATE
linenumberstrue
collapsetrue
curl -X POST \
  http://mr.api.simpledemo.openecomp.org:30227/topics/create \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'cache-control: no-cache' \
  -d '{
	"topicName": "unauthenticated.PNF_UPDATE",
	"topicDescription": "",
	"partitionCount": "",
	"replicationCount": "3"
}'

DCAE

PNF Registration Handler (PRH)

...

 

Update dcae-prh config in Consul

...

BBS-EventProcessor Service (BBS Usecase)https://git.onap.org/dcaegen2/services/plain/components/bbs-event-processor/dpo/blueprints/k8s-bbs-event-processor.yaml-template?h=elalto

https://git.onap.org/dcaegen2/services/plain/components/bbs-event-processor/dpo/blueprints/bbs-event-processor-input.yaml?h=elalto

Code Block
languagebash
themeMidnight
titleBBSep deployment
linenumberstrue
collapsetrue
~/oom/kubernetes# kubectl exec -ti dev-dcaegen2-dcae-bootstrap-85f664d489-54pmt bash
[root@dev-dcaegen2-dcae-bootstrap-779767c49c-7cvdw /]# cfy blueprints validate /blueprints/k8s-bbs-event-processor.yaml
Validating blueprint: /blueprints/k8s-bbs-event-processor.yaml
Blueprint validated successfully
[root@dev-dcaegen2-dcae-bootstrap-779767c49c-7cvdw /]# cfy blueprints upload -b bbs-ep /blueprints/k8s-bbs-event-processor.yaml
Uploading blueprint /blueprints/k8s-bbs-event-processor.yaml...
 k8s-bbs-event-pro... |################################################| 100.0%
Blueprint uploaded. The blueprint's id is bbs-ep
[root@dev-dcaegen2-dcae-bootstrap-779767c49c-7cvdw /]# cfy deployments create -b bbs-ep -i /bbs-event-processor-input.yaml bbs-ep
Creating new deployment from blueprint bbs-ep...
Deployment created. The deployment's id is bbs-ep
[root@dev-dcaegen2-dcae-bootstrap-779767c49c-7cvdw /]# cfy executions start -d bbs-ep install
Executing workflow install on deployment bbs-ep [timeout=900 seconds]
2020-01-13 14:51:54.483  CFY <bbs-ep> Starting 'install' workflow execution
2020-01-13 14:51:55.063  CFY <bbs-ep> [bbs-event-processor_qcbwi6] Creating node instance
2020-01-13 14:51:55.063  CFY <bbs-ep> [bbs-event-processor_qcbwi6.create] Sending task 'k8splugin.create_for_components'
2020-01-13 14:51:59.059  LOG <bbs-ep> [bbs-event-processor_qcbwi6.create] INFO: Done setting up: sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor
2020-01-13 14:51:58.529  LOG <bbs-ep> [bbs-event-processor_qcbwi6.create] INFO: Added config for sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor
2020-01-13 14:51:59.059  CFY <bbs-ep> [bbs-event-processor_qcbwi6.create] Task succeeded 'k8splugin.create_for_components'
2020-01-13 14:51:59.059  CFY <bbs-ep> [bbs-event-processor_qcbwi6] Node instance created
2020-01-13 14:51:59.705  CFY <bbs-ep> [bbs-event-processor_qcbwi6] Configuring node instance: nothing to do
2020-01-13 14:51:59.705  CFY <bbs-ep> [bbs-event-processor_qcbwi6] Starting node instance
2020-01-13 14:51:59.705  CFY <bbs-ep> [bbs-event-processor_qcbwi6.start] Sending task 'k8splugin.create_and_start_container_for_components'
2020-01-13 14:52:01.122  LOG <bbs-ep> [bbs-event-processor_qcbwi6.start] INFO: Starting k8s deployment for sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor, image: nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.components.bbs-event-processor:1.0.0, env: {'CONSUL_HOST': u'consul-server.onap', 'SERVICE_TAGS': 'bbs-ep', 'CONFIG_BINDING_SERVICE': 'config-binding-service'}, kwargs: {'readiness': {u'endpoint': u'/heartbeat', u'type': u'http', u'timeout': u'5s', u'interval': u'180s'}, 'labels': {'cfydeployment': u'bbs-ep', 'cfynodeinstance': u'bbs-event-processor_qcbwi6', 'cfynode': u'bbs-event-processor'}, 'tls_info': {u'use_tls': True, u'cert_directory': u'/opt/app/bbs-event-processor/etc/cert'}, 'envs': {'SERVICE_TAGS': 'bbs-ep'}, 'liveness': {}, 'resource_config': {}, 'volumes': [], 'log_info': {u'log_directory': u'/opt/app/bbs-event-processor/logs'}, 'ports': [u'8100:30810'], 'k8s_location': u'central'}
2020-01-13 14:52:01.837  LOG <bbs-ep> [bbs-event-processor_qcbwi6.start] INFO: Passing k8sconfig: {'tls': {u'cert_path': u'/opt/tls/shared', u'image': u'nexus3.onap.org:10001/onap/org.onap.dcaegen2.deployments.tls-init-container:1.0.3', u'ca_cert_configmap': u'dev-dcaegen2-dcae-bootstrap-dcae-cacert', u'component_ca_cert_path': u'/opt/dcae/cacert/cacert.pem'}, 'filebeat': {u'config_map': u'dcae-filebeat-configmap', u'config_path': u'/usr/share/filebeat/filebeat.yml', u'log_path': u'/var/log/onap', u'image': u'docker.elastic.co/beats/filebeat:5.5.0', u'data_path': u'/usr/share/filebeat/data', u'config_subpath': u'filebeat.yml'}, 'consul_dns_name': u'consul-server.onap', 'image_pull_secrets': [u'onap-docker-registry-key'], 'namespace': u'onap', 'consul_host': 'consul-server:8500', 'default_k8s_location': u'central'}
2020-01-13 14:52:01.837  LOG <bbs-ep> [bbs-event-processor_qcbwi6.start] INFO: k8s deployment initiated successfully for sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor: {'services': ['sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor', 'xsd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor'], 'namespace': u'onap', 'location': u'central', 'deployment': 'dep-sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor'}
2020-01-13 14:52:01.837  LOG <bbs-ep> [bbs-event-processor_qcbwi6.start] INFO: Waiting up to 1800 secs for sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor to become ready
2020-01-13 14:54:45.054  LOG <bbs-ep> [bbs-event-processor_qcbwi6.start] INFO: k8s deployment is ready for: sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor
2020-01-13 14:54:45.586  LOG <bbs-ep> [bbs-event-processor_qcbwi6.start] INFO: Done starting: sd23a0f76c0bf4489b2c221cf88f8af4f-bbs-event-processor
2020-01-13 14:54:45.586  CFY <bbs-ep> [bbs-event-processor_qcbwi6.start] Task succeeded 'k8splugin.create_and_start_container_for_components'
2020-01-13 14:54:45.586  CFY <bbs-ep> [bbs-event-processor_qcbwi6] Node instance started
2020-01-13 14:54:46.303  CFY <bbs-ep> 'install' workflow execution succeeded
Finished executing workflow install on deployment bbs-ep
* Run 'cfy events list -e 08ad7324-4899-4c8e-b84f-6f198e873af1' to retrieve the execution's events/logs

...

See RESTConf Collector (BBS Usecase)https://git.onap.org/dcaegen2/collectors/restconf/plain/dpo/blueprints/k8s-rcc-policy.yaml-template?h=elalto

Code Block
languagebash
themeMidnight
[root@dev-dcaegen2-dcae-bootstrap-779767c49c-7cvdw /]# cfy blueprints validate blueprints/k8s-rcc-policy.yaml
Validating blueprint: blueprints/k8s-rcc-policy.yaml
Blueprint validated successfully
[root@dev-dcaegen2-dcae-bootstrap-779767c49c-7cvdw /]# cfy blueprints upload -b restconfcollector /blueprints/k8s-rcc-policy.yaml
Uploading blueprint /blueprints/k8s-rcc-policy.yaml...
 k8s-rcc-policy.yaml |#################################################| 100.0%
Blueprint uploaded. The blueprint's id is restconfcollector
[root@dev-dcaegen2-dcae-bootstrap-779767c49c-7cvdw /]# cfy deployments create -b restconfcollector
Creating new deployment from blueprint restconfcollector...
Deployment created. The deployment's id is restconfcollector
[root@dev-dcaegen2-dcae-bootstrap-779767c49c-7cvdw /]# cfy executions start -d restconfcollector install
Executing workflow install on deployment restconfcollector [timeout=900 seconds]
2020-01-13 15:12:52.119  CFY <restconfcollector> Starting 'install' workflow execution
2020-01-13 15:12:52.701  CFY <restconfcollector> [rcc_k8s_8qm5me] Creating node instance
2020-01-13 15:12:52.701  CFY <restconfcollector> [rcc_k8s_8qm5me.create] Sending task 'k8splugin.create_for_platforms'
2020-01-13 15:12:55.168  LOG <restconfcollector> [rcc_k8s_8qm5me.create] INFO: Added config for dcaegen2-collectors-rcc
2020-01-13 15:12:55.747  LOG <restconfcollector> [rcc_k8s_8qm5me.create] INFO: Done setting up: dcaegen2-collectors-rcc
2020-01-13 15:12:55.747  CFY <restconfcollector> [rcc_k8s_8qm5me.create] Task succeeded 'k8splugin.create_for_platforms'
2020-01-13 15:12:55.747  CFY <restconfcollector> [rcc_k8s_8qm5me] Node instance created
2020-01-13 15:12:56.341  CFY <restconfcollector> [rcc_k8s_8qm5me] Configuring node instance: nothing to do
2020-01-13 15:12:56.341  CFY <restconfcollector> [rcc_k8s_8qm5me] Starting node instance
2020-01-13 15:12:56.341  CFY <restconfcollector> [rcc_k8s_8qm5me.start] Sending task 'k8splugin.create_and_start_container_for_platforms'
2020-01-13 15:12:57.559  LOG <restconfcollector> [rcc_k8s_8qm5me.start] INFO: Starting k8s deployment for dcaegen2-collectors-rcc, image: nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.restconfcollector:1.1.1, env: {'CONSUL_HOST': u'consul-server.onap.svc.cluster.local', u'DMAAPHOST': u'message-router.onap.svc.cluster.local', 'CONFIG_BINDING_SERVICE': u'config_binding_service', u'CBS_HOST': u'config-binding-service.dcae.svc.cluster.local', u'DMAAPPORT': u'3904', u'CBS_PORT': u'10000', u'CONSUL_PORT': u'8500', u'DMAAPPUBTOPIC': u'unauthenticated.DCAE_RCC_OUTPUT'}, kwargs: {'readiness': {u'endpoint': u'/healthcheck', u'type': u'http', u'timeout': u'1s', u'interval': u'15s'}, 'tls_info': {}, 'replicas': 1, u'envs': {u'CONSUL_HOST': u'consul-server.onap.svc.cluster.local', u'DMAAPHOST': u'message-router.onap.svc.cluster.local', u'CONFIG_BINDING_SERVICE': u'config_binding_service', u'CBS_HOST': u'config-binding-service.dcae.svc.cluster.local', u'DMAAPPORT': u'3904', u'CBS_PORT': u'10000', u'CONSUL_PORT': u'8500', u'DMAAPPUBTOPIC': u'unauthenticated.DCAE_RCC_OUTPUT'}, 'labels': {'cfydeployment': u'restconfcollector', 'cfynodeinstance': u'rcc_k8s_8qm5me', 'cfynode': u'rcc_k8s'}, 'ctx': <cloudify.context.CloudifyContext object at 0x7fb63e5872d0>, 'always_pull_image': False, 'resource_config': {}, 'log_info': {u'log_directory': u'/opt/app/RCCollector/logs'}, u'ports': [u'8080:30416'], 'k8s_location': u'central'}
2020-01-13 15:12:58.275  LOG <restconfcollector> [rcc_k8s_8qm5me.start] INFO: Passing k8sconfig: {'tls': {u'cert_path': u'/opt/tls/shared', u'image': u'nexus3.onap.org:10001/onap/org.onap.dcaegen2.deployments.tls-init-container:1.0.3', u'ca_cert_configmap': u'dev-dcaegen2-dcae-bootstrap-dcae-cacert', u'component_ca_cert_path': u'/opt/dcae/cacert/cacert.pem'}, 'filebeat': {u'config_map': u'dcae-filebeat-configmap', u'config_path': u'/usr/share/filebeat/filebeat.yml', u'log_path': u'/var/log/onap', u'image': u'docker.elastic.co/beats/filebeat:5.5.0', u'data_path': u'/usr/share/filebeat/data', u'config_subpath': u'filebeat.yml'}, 'consul_dns_name': u'consul-server.onap', 'image_pull_secrets': [u'onap-docker-registry-key'], 'namespace': u'onap', 'consul_host': 'consul-server:8500', 'default_k8s_location': u'central'}
2020-01-13 15:12:58.275  LOG <restconfcollector> [rcc_k8s_8qm5me.start] INFO: k8s deployment initiated successfully for dcaegen2-collectors-rcc: {'services': ['dcaegen2-collectors-rcc', 'xdcaegen2-collectors-rcc'], 'namespace': u'onap', 'location': u'central', 'deployment': 'dep-dcaegen2-collectors-rcc'}
2020-01-13 15:12:58.275  LOG <restconfcollector> [rcc_k8s_8qm5me.start] INFO: Waiting up to 1800 secs for dcaegen2-collectors-rcc to become ready
^A2020-01-13 15:13:29.970  LOG <restconfcollector> [rcc_k8s_8qm5me.start] INFO: k8s deployment is ready for: dcaegen2-collectors-rcc
2020-01-13 15:13:30.550  CFY <restconfcollector> [rcc_k8s_8qm5me.start] Task succeeded 'k8splugin.create_and_start_container_for_platforms'
2020-01-13 15:13:30.550  CFY <restconfcollector> [rcc_k8s_8qm5me] Node instance started
2020-01-13 15:13:31.265  CFY <restconfcollector> 'install' workflow execution succeeded
Finished executing workflow install on deployment restconfcollector
* Run 'cfy events list -e 2ea4f906-536b-48b1-aa34-dd6b4baed255' to retrieve the execution's events/logs

...

See VESMapper (BBS Usecase)https://gerrit.onap.org/r/gitweb?p=dcaegen2/services/mapper.git;a=blob_plain;f=UniversalVesAdapter/dpo/blueprints/k8s-vesmapper.yaml-template.yaml

>> nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:1.0.0

VES Collector

Configure mapping VES event domain to DMaaP topic: ves-statechange --> unauthenticated.CPE_AUTHENTICATION

...

Expand
titleHow to deploy policies in Dublin
  1. Package the policy in docker image and then it gets automatically deployed when you call “docker run”. Basically it takes both configuration & model file as arguments while starting the apex engine. This is same as you mentioned below.


  1. Using apex deployment client: Apex-pdp comes with a deployment client UI with which you can connect to a live running apex engine and perform a hot deployment of policy (without any engine restart). This is really helpful for pushing updates to an already running policy or if you just want to start apex engine with configuration file and push the policy later.

Have a look at - https://docs.onap.org/en/casablanca/submodules/policy/apex-pdp.git/docs/APEX-User-Manual.html#the-apex-deployment-client

Note: The clients are not started by default with apex engine. Instead user needs to start the client either locally or inside the container. However, we are planning to package the clients in a separate docker container so that in OOM installations of ONAP we will have it started & ready for use.


  1. Using Policy Distribution: The apex policy (model file) can also be added to the service in SDC and then when user distributes the service, it will be received by the policy-distribution component  inside the distributed CSAR. Which is then parsed and the policy (model file) is deployed in the running apex engine. This way you can deploy policy to running apex engine via Service creation in SDC.

Have a look at - https://docs.onap.org/en/casablanca/submodules/policy/distribution.git/docs/index.html?highlight=distribution

https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Policy+Platform+-+SDC+Service+Distribution+Software+Architecture


  1. Using new Policy Framework architecture: In Dublin release, we have created a new architecture of entire Policy Framework in ONAP. The architecture is based on various microservices having independent responsibilities (API, PAP, PDP etc.). Using this one can create/update policies and deploy them to pdp engines via REST calls. CLAMP will use the REST API’s to deploy policies in pdp engines.

Note: As this is new feature coming in Dublin release, pairwise testing is going on right now and post that official documentation will be created for the same.

In the meantime have a look at - https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Policy+Design+and+API+Flow+for+Model+Driven+Control+Loop

https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/The+ONAP+Policy+Framework

Edge Services: vBNG+AAA+DHCP, Edge SDN M&C

...