Versions Compared

Key

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

Consumed API from other projects

...

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

...

docker201NOTE: Be sure the following are set to match drools-applications and models repocommon1.2 policy/parent
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

https://gerrit.onap.org/r/c/policy/parentdocker/+/104021102678
2a2b

policy/

common

1.

6.

5

all pom.xml's

version.properties

In main pom.xml change the following properties

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

./config/pe/brmsgw.conf:

BRMS_DEPENDENCY_VERSION

BRMS_MODELS_DEPENDENCY_VERSION

https://gerrit.onap.org/r/c/policy/dockercommon/+/102678104047
2b3

policy/

models

2.2.6

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 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/

common

models/+/

104047

104232

34a

policy/modelsapi

2.2.14

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

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/modelsapi/+/104232104257
4a4b

policy/apipap

2.2.03

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/apipap/+/104257104262
4b4c

policy/papdrools-pdp

21.26.03

all pom.xml's

version.properties

In main pom.xml

change the following properties

consider changing the policy.common.version property:

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

Update policy/drools-applications files:

  • pom.xml: version.policy.drools-pdp

https://gerrit.onap.org/r/c/policy/

pap

drools-pdp/+/

104262

104291

4c4d

policy/droolsapex-pdp

12.63.02

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

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

    xacml-pdp

    2.2.2

    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/droolsxacml-pdp/+/104291104294
    4d4f

    policy/apex-pdpdistribution

    2.3.2.0 - In Progress

    all pom.xml's

    version.properties

    In main pom.xml

    consider changing the policy.common.version property:

    change the following properties

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

    policy/xacml-pdp

    2.2.0https://gerrit.onap.org/r/c/policy/distribution/+/104296
    5 - Dependent only on policy/drools-pdp

    policy/drools-applications

    1.6.4

    all pom.xml's

    version.properties

    In main pom.xml

    consider changing the policy.common.version property:

    change the following properties

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

    OOM:

    • 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/xacmldrools-pdpapplications/+/1042944f104408
    6 - Dependent on policy/drools-applications

    policy/distributionengine

    21.36.04

    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/+/1042965 - Dependent only on policy/drools-pdp

    policy/drools-applications

    1.6.0

    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
    • 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

    6 - Dependent on policy/drools-applications

    policy/engine

    1.6.0 - In Progress

    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'

    Code Block
    [gerrit]
    
    host=gerrit.onap.org
    
    port=29418
    
    project=policy/engine.git
    
    defaultbranch=frankfurt

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

    ...



    ...

    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 frankfurt'

    Code Block
    [gerrit]
    
    host=gerrit.onap.org
    
    port=29418
    
    project=policy/engine.git
    
    defaultbranch=frankfurt


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

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


    Steps for Releasing and branching
    1. Go to latest merged review of repo and comment “stage-release
    2. It will trigger2 Jenkins jobs - stage-master & docker-stage-master
    3. Once the jobs are successful, create a yaml filefor releasing maven artifacts firstandraise a review

    4. Once that is merged andbuildis successful, create another container.yaml filefor releasing docker image andraise a review

    NOTE: Drools-applications will require a 2nd "stage-release" to be done after step 3 due to the way it is built. The docker image requires the java artifacts to be released first, which are packaged into the image.

    5. Once that is merged andbuildis successful, goto nexus3.onap.org andverify that the image was released 
    6. Bump the snapshotversiontonextpatchversionandraise a review - I use this command “mvn versions:set -DnewVersion=2.5.1-SNAPSHOT
    7. Once that is merged andbuildis successful, goto gerrit andcreate a “frankfurt” branch. 
    8. Once the branch is created, bump the master branch tonext minor versionusing the same maven command andraise a review 9. Finally goto frankfurt branch andchange the .gitreview fileto point to frankfurt asdefault branch andraise the review.