Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-18

[use case] Workflow orchestration of OpenAPI services

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Blocker
    • 1.24.0
    • None
    • serverless-workflow
    • None
    • False
    • None
    • False
    • 2022 Week 32-34 (from Aug 8)

    Description

      Motivation

      Orchestration is particularly important when it comes to dealing with distributed architecture styles like microservices. At its core, orchestration is a pattern that favors a centralized application workflow. The OpenAPI Specification allows the description of a microservice remote API called from a workflow.

      Operation state and OpenAPI REST function are expected to be one of the most used constructs in serverless workflows

      Goal

      Enable orchestration of OpenAPI microservices in workflows

      Scenarios

      As a developer, I need to combine serverless functions / services / containers to build a serverless application

      As a developer, I need to combine knative services and other kube deployed services to build a workflow

      Expected outcomes

      Workflows use REST functions based on OpenAPI by default

      Workflows can use OpenAPI description files from  URLs or a file system

      Workflows can be defined with operation states which refer to supported function types (rest, expression - other types are tracked in other requirements)

      HTTP Callback requests in Operation state are out of scope (tracked separately)

      Out of scope

      Service discovery of OpenAPI services (SRVCOM-1839)

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6998 [KSW-Guides] Instruct how to have different endpoint configuration profiles for OpenAPI calls

          • 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7261 [KSW-Guides] Orchestration of OpenAPI based services

          • 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.
          • Resolved

          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) KOGITO-6705 [SW]: Enable Caching for OpenAPI documents to avoid rebuilding everytime in Quarkus Dev Mode

          • 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 blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-6811 OpenAPI Gen Migration Quarkus

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-6989 Kogito should be able to generate a proper quarkus image in not writable file systems

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-6564 [SW]: OpenAPI Yaml Operation ID requires special Handling in Function Defitions

          • 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
          is related to

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. SRVLOGIC-5 [core] Service discovery of OpenAPI services in workflows

          • 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

          Activity

            People

              rhn-support-zanini Ricardo Zanini Fernandes
              ibek1@redhat.com Ivo Bek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: