Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-917

BE OOM alignment - update OOM deployment

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Beijing Release
    • None
    • SDC
    • None
    • SDC Sprint 13, SDC Sprint 14, SDC Sprint 15, SDC Sprint 16

       As a user deploying SDC.

      I want our deployment on OOM  to utilize the changes being done in the BE deployment. 

      so that our deployment will be more stable and to allow us in the future to upgrade single components.

      Note: at the moment our deployment needs to work on OOM and Heat. so keep this in mind while making changes.

       

      Flow:

      • BE docker:
        • wait for the C* config  to complete -> wait for the ES config  to complete -> BE docker startup ->   ready probe update state
        • Done for all BE Dockers
      • BE config docker:
        • wait for all BE dockers to be up -> consumer creation ->import / upgrade nominatives -> ready probe update status 
        • Done once 

      DOD:

      1. add BE dependency as ES and C* have started and been configured.
      2. add the use of the BE config docker as dependency on the BE server successful startup.
      3. add a definition of the init job to the k8 template.
      4. add a definition of the be server and the readiness probe to the k8 template.
      5. add a ready check for the BE docker to update that it has successfully started before running the config.
      6. the config docker should run once and only after the BE is ready.
      7. use secret for the SDC default user to access c* in BE server.
      8. update the OOM templates for Beijing only.
      9. check the deployment works.

            af732p af732p
            ml636r ml636r
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: