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

Consumed API from other projects

ProjectAPI DependencyNotes
Portal

2.6.0


AAFv2.1.2
Dmaapv1.1.8


SDC1.6.0
AAI

v16

aai-schema 1.0.3

No direct link to any libraries
SO
REST - No direct link to any libraries
VFC
REST - No direct link to any libraries
SDNR
Dmaap - No direct link to any libraries
SDNC
REST - No direct link to any libraries


Published API - These projects use the policy libraries to build their code

ProjectAPINotes
CLAMPPolicy Lifecycle API

 implemented in own java code


OOFLegacy Policy APIimplemented in own python code
SDNCLegacy Policy APIimplemented in own code
DCAEPolicy Lifecycle APIImplemented own python code


1. Follow the process as outlined here: Independent Versioning and Release Process. Policy repositories inherit from oparent so release jobs will fail if any SNAPSHOT artifact is referenced in the pom.xml's.

  • Verify there are no SNAPSHOTs and we are up-to-date with other team's released artifacts. The CI/CD daily release job does this by automatically failing if a SNAPSHOT is defined in the pom.xml's.
  • Use the Self Releases Workflow (Nexus2) to release artifacts.   Look at comments by Jorge Hernandez  for steps.
  • Update the OOM team K8S Helm Charts.

Note: If using maven version or release plugin, also manually check the versions are set correctly in the POMs, these plugins can miss POMs especially if they do not have Java source code in them.


2. For any new changes to be done post-Release. Then the we must update to the next SNAPSHOT version:

Release OrderRepo (released version)NotesExample Commit(s) for upgrading versions
1

policy/parent

3.1.3

all pom.xml's

version.properties

https://gerrit.onap.org/r/c/policy/parent/+/104021
2a

policy/docker

2.0.1

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version

NOTE: Be sure the following are set to match drools-applications and models repo

./config/pe/brmsgw.conf:

BRMS_DEPENDENCY_VERSION

BRMS_MODELS_DEPENDENCY_VERSION

https://gerrit.onap.org/r/c/policy/docker/+/102678
2b

policy/common

1.6.4

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
https://gerrit.onap.org/r/c/policy/common/+/104047
3

policy/models

2.2.4

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version


  • Ensure that policy/docker/config/pe/brmsgw.conf points to the right version for the CSIT tests to work:

BRMS_MODELS_DEPENDENCY_VERSION

  • Ensure that the policy K8S Helm charts oom/kubernetes/policy/charts/brmsgw/resources/config/pe/brmsgw.conf

BRMS_MODELS_DEPENDENCY_VERSION

  • Ensure that the policy/engine 

    packages/install/src/files/brmsgw.conf - is pointing to the right version


https://gerrit.onap.org/r/c/policy/models/+/104232

4a

policy/api

2.2.2

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/api/+/104257
4b

policy/pap

2.2.1

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/pap/+/104262
4c

policy/drools-pdp

1.6.1

all pom.xml's

version.properties

In main pom.xml consider changing the policy.common.version property:

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version

Update policy/drools-applications dockerfile to pull this image (see below)

Update policy/drools-applications files:

  • pom.xml: version.policy.drools-pdp
  • controlloop/common/feature-controlloop-management/src/test/resources/op.pom

https://gerrit.onap.org/r/c/policy/drools-pdp/+/104291

4d

policy/apex-pdp

2.3.1

all pom.xml's

version.properties

In main pom.xml consider changing the policy.common.version property:

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version

4e

policy/xacml-pdp

2.2.1

all pom.xml's

version.properties

In main pom.xml consider changing the policy.common.version property:

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/xacml-pdp/+/104294
4f

policy/distribution

2.3.1

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
https://gerrit.onap.org/r/c/policy/distribution/+/104296
5 - Dependent only on policy/drools-pdp

policy/drools-applications

1.6.1

all pom.xml's

version.properties

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version
  • version.policy.drools-pdp

Additional files to change in JUnit tests:

controlloop/common/feature-controlloop-management/src/test/resources/op.pom


  • Ensure that policy/docker/config/pe/brmsgw.conf points to the right version for the CSIT tests to work:

BRMS_DEPENDENCY_VERSION

  • Ensure that the policy K8S Helm charts oom/kubernetes/policy/charts/brmsgw/resources/config/pe/brmsgw.conf

BRMS_DEPENDENCY_VERSION

  • Ensure that the policy/engine
    • packages/install/src/files/brmsgw.conf - has the right version

https://gerrit.onap.org/r/c/policy/drools-applications/+/104408
6 - Dependent on policy/drools-applications

policy/engine

1.6.2

all pom.xml's

version.properties

BRMSGateway/config.properties

BRMSGateway/dependency.json

BRMSGateway/src/main/java/org/onap/policy/brms/api/BrmsPush.java

BRMSGateway/src/test/resources/config.properties

packages/base/src/files/install/servers/brmsgw/config.properties

packages/install/src/files/brmsgw.conf

In main pom.xml change the following properties

  • Ensure <parent> tag points to correct policy/parent version
  • policy.common.version
  • policy.models.version


When branching, its easiest to update the .gitreview file ON the new branch in order to ensure that new gerritt submissions are tracked on that branch.

If this is not done, then one should specify the branch when submitting the git review. 'git review elalto'

[gerrit]

host=gerrit.onap.org

port=29418

project=policy/engine.git

defaultbranch=frankfurt


When tagging for a release the following commands should be used:

git tag -sm "6.0.0-ONAP Release" 6.0.0-ONAP
git push <remote-name> 6.0.0-ONAP





  • No labels