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

[SDNC] CM property files not writeable

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • Oslo Release
    • Kohn Release
    • charts
    • Hide

      some property files will be modified after startup of SDNC, e.g.
      /opt/opendaylight/etc/mountpoint-registrar.properties

      or used for further debugging, eg.
      /opt/opendaylight/etc/org.ops4j.pax.logging.cfg

      OOM should handle this. Since k8s CM are not writeable by intention, copy these files as templates into the right place during pod start.

      Command:                                                                                                                                                                                                   │
│       /bin/bash                                                                                                                                                                                                │
│     Args:                                                                                                                                                                                                      │
│       -c                                                                                                                                                                                                       │
│       /opt/onap/sdnc/bin/createLinks.sh ; cp /opt/opendaylight/etc/mountpoint-registrar.properties.template /opt/opendaylight/etc/mountpoint-registrar.properties ; cp /opt/opendaylight/current/etc/org.ops4j │
│ .pax.logging.cfg.template /opt/opendaylight/current/etc/org.ops4j.pax.logging.cfg ;/opt/onap/sdnc/bin/startODL.sh
      Show
      some property files will be modified after startup of SDNC, e.g. /opt/opendaylight/etc/mountpoint-registrar.properties or used for further debugging, eg. /opt/opendaylight/etc/org.ops4j.pax.logging.cfg OOM should handle this. Since k8s CM are not writeable by intention, copy these files as templates into the right place during pod start. Command: │ │ /bin/bash │ │ Args: │ │ -c │ │ /opt/onap/sdnc/bin/createLinks.sh ; cp /opt/opendaylight/etc/mountpoint-registrar.properties.template /opt/opendaylight/etc/mountpoint-registrar.properties ; cp /opt/opendaylight/current/etc/org.ops 4 j │ │ .pax.logging.cfg.template /opt/opendaylight/current/etc/org.ops 4 j.pax.logging.cfg ;/opt/onap/sdnc/bin/startODL.sh

          andreasgeissler Andreas Geissler
          demskeq8 Alexander Dehn
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

            Created:
            Updated:
            Resolved: