Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-1167

Change authoring environment to Controller strategy

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 7.7.0.GA
    • None
    • Cloud
    • None
    • 2020 Week 04-06 (from Jan 20)

    Description

      According to the agreement at the meeting:

      By version 7.7, at least for templates, the Authoring and Authoring HA environments will be changed to use Controller strategy in order to resolve RHDM-1151. (For 7.6, the OSSS limitation, that Deploy might be disabled for some time, will be documented)

      In Operator, maybe OpenShiftStartupStrategy remains default but Controller gets documented? Anyway, Operator will likely be impacted by the upcoming effort to create a unified username/password that will allow easier Controller setup: RHPAM-2175

      Also, for RHDM, when we do this I (Misha) need to document how to change non-HA Authoring template back to OSSS in case we want to use the BC to manage several KIE servers. I understand that it might become easy - possibly just switching some values withough modifying the template itself.

      dward-se-jboss
      evan.zhang@redhat.com
      mfentanes
      jakubschwan
      tohughes
      rhn-support-hjoy

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. RHDM-1151 KIE-Server restarts on OpenShift when doing a deployment from Business Central

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          causes

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2830 Business Central are not synchronised with each other (also Kie Servers)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is documented by

          Sub-task - The sub-task of the issue BXMSDOC-5304 QE review for scope: template authoring document

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBPM-9134 Synchronisation of clustered controllers with Kie servers not working

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2732 Kie Server is not connected to BC in Authoring template

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RHPAM-2175 Adding a system account for connecting to Workbench internal REST/API

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              evan.zhang@redhat.com Evan Zhang (Inactive)
              mramendi Mikhail Ramendik
              Jose Carvajal Hilario Jose Carvajal Hilario
              Jose Carvajal Hilario Jose Carvajal Hilario
              Votes:
              2 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: