Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-2895

Move CSITs to Policy repos

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Medium Medium
    • Honolulu Release
    • None
    • None
    • None
    • Policy 2/5-2/19, Policy 2/25-3/8, Policy 3/16-3/30

      Currently, the code for the Policy CSITs is kept in the integration/csit repo.  Unfortunately, this means that the committers for that repo must approve any changes to CSITs made by any of the ONAP components.  The request has been made to move the component-specific CSITs into repos controlled by committers for those particular components.

      With this in mind, the Policy CSITs should be moved from integration/csit to the policy/docker repo.  However, in the process we'd like to simplify some of the code and replace the robot framework with plain python calls.  Thus it will not be a direct clone, but will likely entail a re-write of the framework, itself.

      Ideas:

      • Perhaps there could be individual run-csit.sh scripts for each component (e.g., api, pap), eliminating the need for separate setup.sh and teardown.sh scripts, as their contents could be rolled into run-csit.sh.  Common stuff be put into other scripts and referenced by run-csit.sh, helping to minimize duplicate code.  Same with shared python code/libraries
      • Subdirectory for each: csit/api, csit/pap
      • Subdirectory for shared items: csit/common or csit/shared
      • Scripts and data files, both, could be placed into the appropriate subdirectory

            takamune_cho takamune_cho
            jrh3 jrh3
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: