aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--checkstyle/pom.xml2
-rw-r--r--docs/clamp/acm/acm-participant-guide.rst33
-rw-r--r--docs/clamp/acm/design-impl/clamp-runtime-acm.rst32
-rw-r--r--docs/development/devtools/testing/csit.rst12
-rw-r--r--docs/development/devtools/testing/s3p/run-s3p.rst45
-rw-r--r--docs/development/prometheus-metrics.rst4
-rw-r--r--docs/drools/pdpdEngine.rst2
-rw-r--r--integration/pom.xml23
-rw-r--r--integration/src/main/resources/release/16.0.0-PF-I1_pf_release_data.csv14
-rw-r--r--integration/src/main/resources/release/pf_release_data.csv25
-rw-r--r--pom.xml2
-rw-r--r--releases/5.1.0.yaml4
-rw-r--r--resources/pom.xml2
-rw-r--r--version.properties2
14 files changed, 131 insertions, 71 deletions
diff --git a/checkstyle/pom.xml b/checkstyle/pom.xml
index acc94c6d..102eeb1e 100644
--- a/checkstyle/pom.xml
+++ b/checkstyle/pom.xml
@@ -23,7 +23,7 @@
<parent>
<groupId>org.onap.policy.parent</groupId>
<artifactId>policy-parent</artifactId>
- <version>5.1.0-SNAPSHOT</version>
+ <version>5.1.1-SNAPSHOT</version>
</parent>
<artifactId>checkstyle</artifactId>
<name>checkstyle</name>
diff --git a/docs/clamp/acm/acm-participant-guide.rst b/docs/clamp/acm/acm-participant-guide.rst
index 56710a4c..05532a02 100644
--- a/docs/clamp/acm/acm-participant-guide.rst
+++ b/docs/clamp/acm/acm-participant-guide.rst
@@ -85,6 +85,39 @@ and the same is configured for the 'ParticipantIntermediaryParameters' object in
typeName: org.onap.policy.clamp.acm.PolicyAutomationCompositionElement
typeVersion: 1.0.0
+Kafka Healthcheck
+-----------------
+
+Optionally is possible to add a Kafka Healthcheck by configuration. That feature is responsible of starting the Kafka configuration.
+If Kafka is not up and Kafka Healthcheck is not enable, Kafka messages configuration will fail.
+This feature check Kafka by an admin connection and if Kafka is up, it will start the Kafka messages configuration,
+but if Kafka is not up yet, it will retry this check later.
+
+Kafka Healthcheck supports the topics check and it could be enabled by configuration (using topicValidation parameter).
+Usually topics are getting created when first message happen, so in that scenario, topicValidation should be set as false.
+In different environment, the two topics will be created manually by a script with specific permissions. So Kafka could be up,
+but the Kafka messages configuration could be fail because the two topics are not get created yet.
+So in that scenario, topicValidation should be set as true, and if topics are not created yet, Healthcheck will retry that check later.
+
+For backward compatibility if Kafka Healthcheck is not configured, it will be disabled and Kafka messages configuration will start as normal.
+
+The following example shows the Kafka Healthcheck configuration.
+
+.. code-block:: bash
+
+ intermediaryParameters:
+ topicValidation: true
+ clampAdminTopics:
+ servers:
+ - ${topicServer:kafka:9092}
+ topicCommInfrastructure: kafka
+ fetchTimeout: 15000
+ topics:
+ operationTopic: policy-acruntime-participant
+ syncTopic: acm-ppnt-sync
+ ........
+
+
Interfaces to Implement
-----------------------
AutomationCompositionElementListener:
diff --git a/docs/clamp/acm/design-impl/clamp-runtime-acm.rst b/docs/clamp/acm/design-impl/clamp-runtime-acm.rst
index 46d4a85f..a3c22e69 100644
--- a/docs/clamp/acm/design-impl/clamp-runtime-acm.rst
+++ b/docs/clamp/acm/design-impl/clamp-runtime-acm.rst
@@ -430,3 +430,35 @@ YAML format is a standard for Automation Composition Type Definition. For the co
text/plain
++++++++++
Text format is used by Prometheus. For the conversion from Object to String will be used **StringHttpMessageConverter**.
+
+JSON log format
+***************
+ACM-runtime supports log in Json format. Below an example of appender for logback configuration to enable it.
+
+.. code-block:: xml
+ :caption: Part of logback configuration
+ :linenos:
+
+ <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
+ <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder">
+ <layout class="org.onap.policy.clamp.acm.runtime.config.LoggingConsoleLayout">
+ <timestampFormat>YYYY-MM-DDThh:mm:ss.sss+/-hh:mm</timestampFormat>
+ <timestampFormatTimezoneId>Etc/UTC</timestampFormatTimezoneId>
+ <staticParameters>service_id=policy-acm|application_id=policy-acm</staticParameters>
+ </layout>
+ </encoder>
+ </appender>
+
+LayoutWrappingEncoder implements the encoder interface and wraps the Java class LoggingConsoleLayout as layout to which it delegates the work of transforming an event into Json string.
+Parameters for LoggingConsoleLayout:
+
+- *timestampFormat*: Timestamp Format
+- *timestampFormatTimezoneId*: Time Zone used in the Timestamp Format
+- *staticParameters*: List of parameters do add into the log separated with a "|"
+
+Below un example of result:
+
+.. code-block:: json
+
+ {"severity":"INFO","extra_data":{"logger":"network","thread":"KAFKA-source-policy-acruntime-participant"},"service_id":"policy-acm","message":"[IN|KAFKA|policy-acruntime-participant]\n{\"state\":\"ON_LINE\",\"participantDefinitionUpdates\":[],\"automationCompositionInfoList\":[],\"participantSupportedElementType\":[{\"id\":\"f88c4463-f012-42e1-8927-12b552ecf380\",\"typeName\":\"org.onap.policy.clamp.acm.K8SMicroserviceAutomationCompositionElement\",\"typeVersion\":\"1.0.0\"}],\"messageType\":\"PARTICIPANT_STATUS\",\"messageId\":\"d3dc2f86-4253-4520-bbac-97c4c04547ad\",\"timestamp\":\"2025-01-21T16:14:27.087474035Z\",\"participantId\":\"101c62b3-8918-41b9-a747-d21eb79c6c93\",\"replicaId\":\"c1ba61d2-1dbd-44e4-80bd-135526c0615f\"}","application_id":"policy-acm","timestamp":"2025-01-21T16:14:27.114851006Z"}
+ {"severity":"INFO","extra_data":{"logger":"network","thread":"KAFKA-source-policy-acruntime-participant"},"service_id":"policy-acm","message":"[IN|KAFKA|policy-acruntime-participant]\n{\"state\":\"ON_LINE\",\"participantDefinitionUpdates\":[],\"automationCompositionInfoList\":[],\"participantSupportedElementType\":[{\"id\":\"4609a119-a8c7-41ee-96d1-6b49c3afaf2c\",\"typeName\":\"org.onap.policy.clamp.acm.HttpAutomationCompositionElement\",\"typeVersion\":\"1.0.0\"}],\"messageType\":\"PARTICIPANT_STATUS\",\"messageId\":\"ea29ab01-665d-4693-ab17-3a72491b5c71\",\"timestamp\":\"2025-01-21T16:14:27.117716317Z\",\"participantId\":\"101c62b3-8918-41b9-a747-d21eb79c6c91\",\"replicaId\":\"5e4f9690-742d-4190-a439-ebb4c820a010\"}","application_id":"policy-acm","timestamp":"2025-01-21T16:14:27.144379028Z"}
diff --git a/docs/development/devtools/testing/csit.rst b/docs/development/devtools/testing/csit.rst
index ede88af1..f5cd8eaa 100644
--- a/docs/development/devtools/testing/csit.rst
+++ b/docs/development/devtools/testing/csit.rst
@@ -138,12 +138,12 @@ Different from Docker usage, the microk8s installation is not removed when tests
Installing all available PF components
--------------------------------------
-Use the `run-k8s-csit.sh` script to install PF components with Prometheus server available.
+Use the `cluster_setup.sh` script to install PF components with Prometheus server available.
.. code-block:: bash
- cd ~/git/policy/docker
- ./csit/run-k8s-csit.sh install
+ cd ~/git/policy/docker/csit/resources/scripts
+ ./cluster_setup.sh install
In this case, no tests are executed and the environment can be used for other integration tests
@@ -156,7 +156,7 @@ Uninstall and clean up
If running the CSIT tests with microk8s environment, docker images for the tests suites are created.
To clean them up, user `docker prune <https://docs.docker.com/config/pruning/>`_ command.
-To uninstall policy helm deployment and/or the microk8s cluster, use `run-k8s-csit.sh`
+To uninstall policy helm deployment and/or the microk8s cluster, use `cluster_setup.sh`
.. code-block:: bash
@@ -164,10 +164,10 @@ To uninstall policy helm deployment and/or the microk8s cluster, use `run-k8s-cs
cd ~/git/policy/docker
# to uninstall deployment
- ./csit/run-k8s-csit.sh uninstall
+ ./csit/resources/scripts/cluster_setup.sh uninstall
# to remove cluster
- ./csit/run-k8s-csit.sh clean
+ ./csit/resources/scripts/cluster_setup.sh clean
End of document \ No newline at end of file
diff --git a/docs/development/devtools/testing/s3p/run-s3p.rst b/docs/development/devtools/testing/s3p/run-s3p.rst
index 17eba32a..1ac88442 100644
--- a/docs/development/devtools/testing/s3p/run-s3p.rst
+++ b/docs/development/devtools/testing/s3p/run-s3p.rst
@@ -6,11 +6,11 @@ Running the Policy Framework S3P Tests
Per release, the policy framework team perform stability and performance tests per component of the policy framework.
This testing work involves performing a series of test on a full OOM deployment and updating the various test plans to work towards the given deployment.
-This work can take some time to setup before performing any tests to begin with.
+This work can take some time to setup to begin with, before performing any tests.
For stability testing, a tool called JMeter is used to trigger a series of tests for a period of 72 hours which has to be manually initiated and monitored by the tester.
-Likewise, with the performance tests, but in this case for ~2 hours.
-As part of the work to make to automate this process a script can be now triggered to bring up a microk8s cluster on a VM, install JMeter, alter the cluster info to match the JMX test plans for JMeter to trigger and gather results at the end.
-These S3P tests will be triggered for a shorter period as part of the CSITs to prove the stability and performance of our components.
+Likewise, the performance tests run in the same manner but for a shorter time of ~2 hours.
+As part of the work to automate this process a script can be now triggered to bring up a microk8s cluster on a VM, install JMeter, alter the cluster info to match the JMX test plans for JMeter to trigger and gather results at the end.
+These S3P tests will be triggered for a shorter period as part of the GHAs to prove the stability and performance of our components.
There has been recent work completed to trigger our CSIT tests in a K8s environment.
As part of this work, a script has been created to bring up a microk8s cluster for testing purposes which includes all necessary components for our policy framework testing.
@@ -19,34 +19,15 @@ Once this cluster is brought up, a script is called to alter the cluster.
The IPS and PORTS of our policy components are set by this script to ensure consistency in the test plans.
JMeter is installed and the S3P test plans are triggered to run by their respective components.
-.. code-block:: bash
- :caption: Start S3P Script
+`run-s3p-tests.sh <https://github.com/onap/policy-docker/blob/master/csit/run-s3p-tests.sh>`_
- #===MAIN===#
- if [ -z "${WORKSPACE}" ]; then
- export WORKSPACE=$(git rev-parse --show-toplevel)
- fi
- export TESTDIR=${WORKSPACE}/testsuites
- export API_PERF_TEST_FILE=$TESTDIR/performance/src/main/resources/testplans/policy_api_performance.jmx
- export API_STAB_TEST_FILE=$TESTDIR/stability/src/main/resources/testplans/policy_api_stability.jmx
- if [ $1 == "run" ]
- then
- mkdir automate-performance;cd automate-performance;
- git clone "https://gerrit.onap.org/r/policy/docker"
- cd docker/csit
- if [ $2 == "performance" ]
- then
- bash start-s3p-tests.sh run $API_PERF_TEST_FILE;
- elif [ $2 == "stability" ]
- then
- bash start-s3p-tests.sh run $API_STAB_TEST_FILE;
- else
- echo "echo Invalid arguments provided. Usage: $0 [option..] {performance | stability}"
- fi
- else
- echo "Invalid arguments provided. Usage: $0 [option..] {run | uninstall}"
- fi
+This script automates the setup, execution, and teardown of S3P tests for policy components.
+It initializes a Kubernetes environment, installs Apache JMeter for running test plans, and executes specified JMX test files.
+The script logs all operations, tracks errors, warnings, and processed files, and provides a summary report upon completion.
+It includes options to either run tests (test <jmx_file>) or clean up the environment (clean). The clean option uninstalls the Kubernetes cluster and removes temporary resources.
+The script also ensures proper resource usage tracking and error handling throughout its execution.
-This script is triggered by each component.
-It will export the performance and stability testplans and trigger the start-s3p-test.sh script which will perform the steps to automatically run the s3p tests.
+`run-s3p-test.sh <https://github.com/onap/policy-api/blob/master/testsuites/run-s3p-test.sh>`_
+In summary, this script automates running performance or stability tests for a Policy Framework component by setting up necessary directories, cloning the required docker repository, and executing predefined test plans.
+It also provides a clean-up option to remove resources after testing. \ No newline at end of file
diff --git a/docs/development/prometheus-metrics.rst b/docs/development/prometheus-metrics.rst
index 74532311..e7d4d3a6 100644
--- a/docs/development/prometheus-metrics.rst
+++ b/docs/development/prometheus-metrics.rst
@@ -188,6 +188,6 @@ Key metrics for Policy Distribution
===================================================================
Policy Framework uses ServiceMonitor custom resource definition (CRD) to allow Prometheus to monitor the services it exposes. Label selection is used to determine which services are selected to be monitored.
-For label management and troubleshooting refer to the documentation at: `Prometheus operator <https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/troubleshooting.md>`__.
+For label management and troubleshooting refer to the documentation at: `Prometheus operator <https://github.com/prometheus-operator/prometheus-operator/tree/main/Documentation>`__.
-`OOM charts <https://github.com/onap/oom/tree/master/kubernetes/policy/components>`__ for policy include ServiceMonitor and properties can be overrided based on the deployment specifics.
+`OOM charts <https://github.com/onap/oom/tree/master/kubernetes/policy/components>`__ for policy include ServiceMonitor and properties can be overwritten based on the deployment specifics.
diff --git a/docs/drools/pdpdEngine.rst b/docs/drools/pdpdEngine.rst
index 6397dd86..7a699025 100644
--- a/docs/drools/pdpdEngine.rst
+++ b/docs/drools/pdpdEngine.rst
@@ -761,7 +761,7 @@ Data Migration
PDP-D data used to be migrated across releases with its own db-migrator until Kohn release. Since
Oslo, the main policy database manager,
-`db-migrator <https://git.onap.org/policy/docker/tree/policy-db-migrator/src/main/docker/db-migrator>`_
+`db-migrator <https://git.onap.org/policy/docker/tree/policy-db-migrator/>`_
has been in use.
The migration occurs when different release data is detected. *db-migrator* will look under the
diff --git a/integration/pom.xml b/integration/pom.xml
index f48b7d0f..ac9f3046 100644
--- a/integration/pom.xml
+++ b/integration/pom.xml
@@ -2,7 +2,7 @@
============LICENSE_START=======================================================
Copyright (C) 2018 Ericsson. All rights reserved.
Modifications Copyright (C) 2018-2023 AT&T. All rights reserved.
- Modifications Copyright (C) 2019-2024 Nordix Foundation.
+ Modifications Copyright (C) 2019-2025 Nordix Foundation.
Modifications Copyright (C) 2020-2022 Bell Canada.
================================================================================
Licensed under the Apache License, Version 2.0 (the "License");
@@ -29,7 +29,7 @@
<parent>
<groupId>org.onap.policy.parent</groupId>
<artifactId>policy-parent</artifactId>
- <version>5.1.0-SNAPSHOT</version>
+ <version>5.1.1-SNAPSHOT</version>
</parent>
<artifactId>integration</artifactId>
<packaging>pom</packaging>
@@ -38,7 +38,7 @@
<properties>
<java.version>17</java.version>
<!-- Note Well: For RELEASE/SNAPSHOT always set to the project version -->
- <version.parent.resources>5.0.2-SNAPSHOT</version.parent.resources>
+ <version.parent.resources>5.1.1-SNAPSHOT</version.parent.resources>
<version.parent.checkstyle>[4.1.2,)</version.parent.checkstyle>
<jacoco.destFile>${project.build.directory}/code-coverage/jacoco-ut.exec</jacoco.destFile>
<!-- Default Sonar configuration -->
@@ -75,7 +75,7 @@
<version.kafka>3.8.1</version.kafka>
<version.kotlin>2.0.20</version.kotlin>
<version.log4j>2.23.1</version.log4j>
- <version.logback>1.5.12</version.logback>
+ <version.logback>1.5.15</version.logback>
<version.maven-checkstyle-plugin>3.3.1</version.maven-checkstyle-plugin>
<version.maven-remote-resources-plugin>3.1.0</version.maven-remote-resources-plugin>
<version.micrometer>1.13.6</version.micrometer>
@@ -89,10 +89,10 @@
<version.sdc-dist>2.1.1</version.sdc-dist>
<version.sdc-tosca>1.9.0</version.sdc-tosca>
<version.slf4j>2.0.13</version.slf4j>
- <version.spring>6.1.14</version.spring>
- <version.springboot>3.3.5</version.springboot>
- <version.spring-data>3.3.5</version.spring-data>
- <version.spring-security>6.3.4</version.spring-security>
+ <version.spring>6.1.16</version.spring>
+ <version.springboot>3.3.7</version.springboot>
+ <version.spring-data>3.3.7</version.spring-data>
+ <version.spring-security>6.3.6</version.spring-security>
<version.sonar>3.11.0.3922</version.sonar>
<version.swagger.codegen.v3>3.0.52</version.swagger.codegen.v3>
<version.swagger.core.v3>2.2.25</version.swagger.core.v3>
@@ -512,7 +512,7 @@
<dependency>
<groupId>org.apache.tomcat.embed</groupId>
<artifactId>tomcat-embed-core</artifactId>
- <version>10.1.31</version>
+ <version>10.1.34</version>
</dependency>
<dependency>
<groupId>org.aspectj</groupId>
@@ -680,11 +680,6 @@
<version>${version.drools}</version>
</dependency>
<dependency>
- <groupId>org.mariadb.jdbc</groupId>
- <artifactId>mariadb-java-client</artifactId>
- <version>3.3.3</version>
- </dependency>
- <dependency>
<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>42.7.2</version>
diff --git a/integration/src/main/resources/release/16.0.0-PF-I1_pf_release_data.csv b/integration/src/main/resources/release/16.0.0-PF-I1_pf_release_data.csv
new file mode 100644
index 00000000..b486e87f
--- /dev/null
+++ b/integration/src/main/resources/release/16.0.0-PF-I1_pf_release_data.csv
@@ -0,0 +1,14 @@
+Repo, Last Tag Version,Snapshot Version,Changed Files,Docker Images
+policy/parent,5.1.0,5.1.1-SNAPSHOT,0,
+policy/docker,4.1.0,4.1.1-SNAPSHOT,1,'policy-jre-alpine':'policy-jdk-alpine':'policy-db-migrator'
+policy/common,3.1.0,3.1.1-SNAPSHOT,0,
+policy/models,4.1.0,4.1.1-SNAPSHOT,2,'policy-models-simulator'
+policy/api,4.1.0,4.1.1-SNAPSHOT,1,'policy-api'
+policy/pap,4.1.0,4.1.1-SNAPSHOT,1,'policy-pap'
+policy/apex-pdp,4.1.0,4.1.1-SNAPSHOT,1,'policy-apex-pdp'
+policy/drools-pdp,3.1.0,3.1.1-SNAPSHOT,1,'policy-drools'
+policy/xacml-pdp,4.1.0,4.1.1-SNAPSHOT,1,'policy-xacml-pdp'
+policy/distribution,4.1.0,4.1.1-SNAPSHOT,1,'policy-distribution'
+policy/clamp,8.1.0,8.1.1-SNAPSHOT,8,'policy-clamp-ac-pf-ppnt':'policy-clamp-ac-k8s-ppnt':'policy-clamp-ac-http-ppnt':'policy-clamp-ac-a1pms-ppnt':'policy-clamp-runtime-acm':'policy-clamp-acm-element-impl':'policy-clamp-ac-kserve-ppnt':'policy-clamp-ac-sim-ppnt'
+policy/drools-applications,3.1.0,3.1.1-SNAPSHOT,0,'policy-pdpd-cl'
+policy/opa-pdp,1.0.0,1.0.1-SNAPSHOT,1,'policy-opa-pdp'
diff --git a/integration/src/main/resources/release/pf_release_data.csv b/integration/src/main/resources/release/pf_release_data.csv
index 343752b5..b486e87f 100644
--- a/integration/src/main/resources/release/pf_release_data.csv
+++ b/integration/src/main/resources/release/pf_release_data.csv
@@ -1,13 +1,14 @@
Repo, Last Tag Version,Snapshot Version,Changed Files,Docker Images
-policy/parent,5.0.1,5.1.0-SNAPSHOT,0,
-policy/docker,4.0.1,4.1.0-SNAPSHOT,1,'policy-jre-alpine':'policy-jdk-alpine':'policy-db-migrator'
-policy/common,3.0.1,3.1.0-SNAPSHOT,0,
-policy/models,4.0.1,4.1.0-SNAPSHOT,2,'policy-models-simulator'
-policy/api,4.0.1,4.1.0-SNAPSHOT,1,'policy-api'
-policy/pap,4.0.1,4.1.0-SNAPSHOT,1,'policy-pap'
-policy/apex-pdp,4.0.1,4.1.0-SNAPSHOT,1,'policy-apex-pdp'
-policy/drools-pdp,3.0.1,3.1.0-SNAPSHOT,1,'policy-drools'
-policy/xacml-pdp,4.0.1,4.1.0-SNAPSHOT,1,'policy-xacml-pdp'
-policy/distribution,4.0.1,4.1.0-SNAPSHOT,1,'policy-distribution'
-policy/clamp,8.0.1,8.1.0-SNAPSHOT,8,'policy-clamp-ac-pf-ppnt':'policy-clamp-ac-k8s-ppnt':'policy-clamp-ac-http-ppnt':'policy-clamp-ac-a1pms-ppnt':'policy-clamp-runtime-acm':'policy-clamp-acm-element-impl':'policy-clamp-ac-kserve-ppnt':'policy-clamp-ac-sim-ppnt'
-policy/drools-applications,3.0.1,3.1.0-SNAPSHOT,0,'policy-pdpd-cl'
+policy/parent,5.1.0,5.1.1-SNAPSHOT,0,
+policy/docker,4.1.0,4.1.1-SNAPSHOT,1,'policy-jre-alpine':'policy-jdk-alpine':'policy-db-migrator'
+policy/common,3.1.0,3.1.1-SNAPSHOT,0,
+policy/models,4.1.0,4.1.1-SNAPSHOT,2,'policy-models-simulator'
+policy/api,4.1.0,4.1.1-SNAPSHOT,1,'policy-api'
+policy/pap,4.1.0,4.1.1-SNAPSHOT,1,'policy-pap'
+policy/apex-pdp,4.1.0,4.1.1-SNAPSHOT,1,'policy-apex-pdp'
+policy/drools-pdp,3.1.0,3.1.1-SNAPSHOT,1,'policy-drools'
+policy/xacml-pdp,4.1.0,4.1.1-SNAPSHOT,1,'policy-xacml-pdp'
+policy/distribution,4.1.0,4.1.1-SNAPSHOT,1,'policy-distribution'
+policy/clamp,8.1.0,8.1.1-SNAPSHOT,8,'policy-clamp-ac-pf-ppnt':'policy-clamp-ac-k8s-ppnt':'policy-clamp-ac-http-ppnt':'policy-clamp-ac-a1pms-ppnt':'policy-clamp-runtime-acm':'policy-clamp-acm-element-impl':'policy-clamp-ac-kserve-ppnt':'policy-clamp-ac-sim-ppnt'
+policy/drools-applications,3.1.0,3.1.1-SNAPSHOT,0,'policy-pdpd-cl'
+policy/opa-pdp,1.0.0,1.0.1-SNAPSHOT,1,'policy-opa-pdp'
diff --git a/pom.xml b/pom.xml
index af01d0a4..c65e1174 100644
--- a/pom.xml
+++ b/pom.xml
@@ -24,7 +24,7 @@
<modelVersion>4.0.0</modelVersion>
<groupId>org.onap.policy.parent</groupId>
<artifactId>policy-parent</artifactId>
- <version>5.1.0-SNAPSHOT</version>
+ <version>5.1.1-SNAPSHOT</version>
<packaging>pom</packaging>
<properties>
diff --git a/releases/5.1.0.yaml b/releases/5.1.0.yaml
new file mode 100644
index 00000000..381ee6f9
--- /dev/null
+++ b/releases/5.1.0.yaml
@@ -0,0 +1,4 @@
+distribution_type: 'maven'
+version: '5.1.0'
+project: 'policy-parent'
+log_dir: 'policy-parent-maven-stage-master/1420/'
diff --git a/resources/pom.xml b/resources/pom.xml
index 35f07ee7..37f77c8c 100644
--- a/resources/pom.xml
+++ b/resources/pom.xml
@@ -25,7 +25,7 @@
<parent>
<groupId>org.onap.policy.parent</groupId>
<artifactId>policy-parent</artifactId>
- <version>5.1.0-SNAPSHOT</version>
+ <version>5.1.1-SNAPSHOT</version>
</parent>
<artifactId>policy-parent-resources</artifactId>
diff --git a/version.properties b/version.properties
index 28e55175..98a488c3 100644
--- a/version.properties
+++ b/version.properties
@@ -4,7 +4,7 @@
major=5
minor=1
-patch=0
+patch=1
base_version=${major}.${minor}.${patch}