Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-1610

Make OOM charts compatible with offline installer

XMLWordPrintable

    • Make OOM charts compatible with offline installer
    • Done

      there were couple of places in OOM charts we need to patch in Beijing to be able to spawn and configure pods properly for offline deployments. Following patchfile was applied in Beijing therefore:
      https://gerrit.onap.org/r/gitweb?p=oom/offline-installer.git;a=blob;f=patches/offline-changes.patch;h=5238da4272f42443a118a0b3d3d51e5b33f21801;hb=refs/heads/beijing

      and bash offline installer was further processing/configuring pods see:
      https://gerrit.onap.org/r/gitweb?p=oom/offline-installer.git;a=blob;f=bash/tools/common-functions.sh;h=5563b047e8afaf88c8225e1795e5c7faf4cd20d7;hb=refs/heads/beijing#l637
      patch_npm_oom()
      patch_spring_oom()
      patch_cfy_manager_depl()

      In casablanca it's probably too late to cover those parts but we can address this topic during Dublin lifecycle, we believe that changes in there are generic and would be relevant for any other offline deployment so we should find a way how to do needed directly in OOM w/o patching it.

      Example of changes required:

      1) setting-up own NPM registry for sdnc-portal and appc-dgbuilder/sdnc-dgbuilder

      • common/dgbuilder/templates/deployment.yaml
      • sdnc/charts/sdnc-portal/templates/deployment.yaml

      2) set cert-path for cloudify

      • dcaegen2/charts/dcae-cloudify-manager/templates/deployment.yaml

      3) special handling for sdnc-ansible-server (in casablanca there is also appc-ansible-server)
      this is typical example of wrongly written logic, a lot of debian & npm package are downloaded from latest repos in runtime (in Beijing there was also issue that after some time it was not able to initialize sdnc-builder properly because image became incompatible with latest packages being downloaded)

      • kubernetes/sdnc/charts/sdnc-ansible-server/templates/deployment.yaml

      4) need to add own cert handling
      oom/kubernetes/common/common/templates/_cacert.tpl
      oom/kubernetes/onap/templates/configmap.yaml

      5) policy related changes

      • there are couple of files in policy component which has to be modified to get own certificate for our offline nexus trusted and mainly maven artifacts are then downloaded from trusted source
        oom/kubernetes/policy/charts/brmsgw/templates/deployment.yaml
        oom/kubernetes/policy/charts/drools/templates/statefulset.yaml
        oom/kubernetes/policy/charts/pdp/templates/statefulset.yaml
        oom/kubernetes/policy/charts/policy-common/templates/_keystore.tpl
        oom/kubernetes/policy/templates/deployment.yaml

            tomas.levora tomas.levora
            michal.ptacek michal.ptacek
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: