Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2566

Change authoring environment to Controller strategy

    XMLWordPrintable

Details

    • Task
    • Resolution: Duplicate
    • Major
    • None
    • None
    • None
    • None

    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. I could not find the JIRA, I would appreciate if someone could mention it in comments.

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

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. RHPAM-2567 Remove ReadWriteMany requirement from non-HA Authoring environment and switch all Authoring templates to Controller strategy

          • 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

          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
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: