Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-898

ONAP Deployment Resiliency changes to deploy without POD failures

    XMLWordPrintable

Details

    • Story
    • Status: Closed
    • High
    • Resolution: Won't Do
    • None
    • El Alto Release

    Description

      see https://wiki.onap.org/display/DW/Cloud+Native+Deployment#CloudNativeDeployment-DeploymentIntegritybasedonPodDependencies

       

      Need 3 things - patches for 2

      • 13+1 node cluster up on openstack – working today - I have a heat template to upload
      • Deployment completes out of the box – demo’d yesterday with timing adjustments
      • vFW working – working now
      • also
      • Nexus3 proxy instructions – gathering
      • Docker pre pull script – I can get this together via the manifest

      20190106
      dcae will need to come in early - after dmaap - it it is deployed late in the cycle - the secondary cloudify orchestration times out

      nap          dep-config-binding-service-ff8c4d8dd-cn99q              2/2       Running            0          12h
onap          dep-dcae-datafile-collector-7464dc476c-nrpjj            2/2       Running            0          12h
onap          dep-dcae-hv-ves-collector-5fd547d66-hzjh8               2/2       Running            0          12h
onap          dep-dcae-prh-67fb586888-7gg7q                           2/2       Running            0          12h
onap          dep-dcae-snmptrap-collector-7fc4d645c5-pmvz9            1/1       Running            0          12h
onap          dep-dcae-tca-analytics-7694f7bfc6-dpdsk                 2/2       Running            0          12h
onap          dep-dcae-ves-collector-86c97bf9bb-rpbw5                 2/2       Running            0          12h
onap          dep-deployment-handler-7fb4755fd8-2tf5k                 2/2       Running            0          12h
onap          dep-holmes-engine-mgmt-6946dd586d-5699w                 1/1       Running            0          12h
onap          dep-holmes-rule-mgmt-7f576bd888-mv4px                   1/1       Running            0          12h
onap          dep-inventory-69c6bd5bb6-shgd7                          1/1       Running            1          12h
onap          dep-policy-handler-697ddf7fd4-8mhfz                     2/2       Running            0          12h
onap          dep-pstg-write-f67b57947-xkkrr                          1/1       Running            0          12h
onap          dep-service-change-handler-6848796d76-xx6c2             1/1       Running            19         12h

       

      Attachments

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. VVP-176 Re-enable VVP in Dublin for Kubernetes deployment

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-707 Logging El-Alto (moved from) Dublin Scope

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1580 HELM undeploy may hang on Terminating pods that need a --purge

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. AAI-2076 A&AI healthcheck timeout

          • Highest - Catastrophic defect that causes total failure of the software or unrecoverable data loss with no available workaround. Complete shut-down of the process, nothing can proceed further. Blocks testing of the product / feature. Must be fixed in the next build.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. LOG-913 POMBA: 1 of 11 pods failing on sequenced startup on 3.0.0-ONAP - pomba is 22 on the order - looks timing related

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. TSC-79 LF Nexus3 routing slowdown starting 20181217 - 80-100x slower download times totalling 120+ hours - using nexus3/4.onap.cloud proxy for now

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. TSC-92 Casablanca RM branch stability before 3.0.1-ONAP tagging - helm deploy/hc before merging

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. AAI-2079 aai-traversal and aai container failure to deploy issues in casablanca 3.0.0-ONAP

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. DCAEGEN2-1067 Deploying DCAEGEN2 late in a sequenced deployment will cause the secondary cloudify orchestration pods DEP* to fail

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. DCAEGEN2-1068 DCAEGEN2 failed redeployment leaves cloudify orchestrated dev-dcae namespace pods up

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. DMAAP-1048 [DR] AAF certs expired on dmaap-dr-prov and dmaap-dr-node

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Sub-task - The sub-task of the issue LOG-905 docker_prepull.sh script for casablanca

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Sub-task - The sub-task of the issue LOG-924 Kubernetes chart dependencies - make all 105 in 87 files conditional - post yaml for cd

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1089 DCAE pods are not getting purged

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Task - A task that needs to be done. OOM-1586 Add --force --grace-period=0 delete pod capability to cd.sh script

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TSC-101 Dublin kubernetes deployment stability tracking

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. VVP-130 DEV mode dev.yaml override for all remaining ReplicaSet counts still above 1

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          is duplicated by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OOM-1547 ONAP consistent deployment of pods in dependency order - to avoid failed random deployments

          • Highest - Catastrophic defect that causes total failure of the software or unrecoverable data loss with no available workaround. Complete shut-down of the process, nothing can proceed further. Blocks testing of the product / feature. Must be fixed in the next build.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OOM-1547 ONAP consistent deployment of pods in dependency order - to avoid failed random deployments

          • Highest - Catastrophic defect that causes total failure of the software or unrecoverable data loss with no available workaround. Complete shut-down of the process, nothing can proceed further. Blocks testing of the product / feature. Must be fixed in the next build.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OOM-1543 Helm deploy/undeploy adjustments for triage of failed/unlisted deployments

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-899 ONAP vFW vFirewall Use Case validation - so we can use it for transaction tracing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1559 dmaap-dr-prov deployment is failing - master

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1560 dmaap-dr-node deployment is failing - casablanca

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. INT-943 Bring Pomba docker image versions in docker-manifest-staging.csv in sync with OOM charts

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Task - A task that needs to be done. LOG-352 Docker prepull strategy for multi-node clusters

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-371 K8S DevOps: add Nexus3 proxy helm chart

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-375 Nexus3.onap.info public proxy for throughput

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. LOG-862 Log project pods take a lot of CPU in full ONAP deployment

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Sub-task - The sub-task of the issue OOM-1549 Dashboard OOM deployment

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1550 Docs: kubernetes host registration must use private network IP not public - swap out screencap

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          links to

          Web Link https://gerrit.onap.org/r/#/c/75422/

          Web Link https://lists.onap.org/g/onap-discuss/topic/how_to_test_onap_casablanca/28996873?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,28996873

          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          # Subject Branch Project Status CR V
          74827,2 adjust cd.sh for deploy seq timing master logging-analytics Status: ABANDONED -1 +1
          75098,4 cd adjust for random deploy upgrade conflict master logging-analytics Status: MERGED +2 +1
          75422,8 adjust cd.sh for managed seq deploy master logging-analytics Status: MERGED +2 +1

          Activity

            People

              michaelobrien Michael O'Brien
              michaelobrien Michael O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: