Skip to content

Latest commit

 

History

History
86 lines (70 loc) · 4.66 KB

QUARKUS-2284.md

File metadata and controls

86 lines (70 loc) · 4.66 KB
Raw

QUARKUS-2284 OpenShift Serverless is requesting that we support it when using OpenShift Serverless Functions

Jira: https://issues.redhat.com/browse/QUARKUS-2284

This feature is about productization of Quarkus Funqy and Quarkus Funqy Knative Events Binding extensions needed by OpenShift Serverless Functions. We should create multiple Quarkus functions deployed with Quarkus OpenShift extension as a single application. Broker and triggers are going to be created and deleted with Knative Client (kn) and Knative Java Client. Functions should be used with Knative Eventing, test both native and JVM mode and verify Funqy features. Before we can do that, we need to install Knative Eventing with our Quarkus QE Framework as we want the Test Suite to work without any prerequisites and the operator starts several pods that would keep running.

Scope of the testing

Tests should verify:

  • Quarkus function deployment using Quarkus OpenShift extension
  • Invoking Quarkus functions:
    • JSON object in the body of the request (HTTP POST request)
    • Data in the query string (HTTP GET request)
    • JSON object in the data property (CloudEvent)
  • Quarkus function receives and processes:
    • bean (f.e. POJO)
    • CloudEvent using the Funqy @Context annotation
    • binary data
    • primitive type or its wrapper
  • Reading and writing of the attributes of a CloudEvent
  • Permitted return types:
    • void
    • String
    • byte[]
    • primitive type and its wrapper
    • Javabeans, maps, lists, arrays
    • CloudEvents<E>
    • Uni<T>, where T is any of types listed above
  • Quarkus function accepts events from custom resource created by us as well as from Event Sources provided out of the box
  • Cloud Event type and source matching:
    • default mapping when the type match the function name for the function to trigger
    • mapping changed by configuration within application.properties
    • mapping with @CloudEventMapping annotation
  • Complex function chain, when one function triggers the next and so on
  • DEV mode and unit testing using RestAssured using:
    • normal HTTP requests
    • Cloud Event Binary mode
    • Structured Mode
  • Multiple functions declared in one application
  • Accessing secrets and config maps from functions

Impact on test suites and testing automation

  • One new module will be added to our Test Suite:
    • Bare metal tests that cover DEV mode (JVM mode only)
    • OpenShift tests for Funqy applications deployed as OpenShift Serverless Functions in JVM and native mode

Impact on resources:

  • Impact on lab capacity is one medium size executor
  • Required additional time for the test execution should be up to 10 minutes. Roughly we expect 3 min. for JVM mode and 8 min. for native mode:
    • ~ 1 minute to create broker and triggers
    • ~ 2/7 minutes to build and deploy a function in JVM/native mode
  • Knative Eventing API must be installed on our OpenShift clusters as shared namespace (knative-eventing) is used by all tests

Getting familiar with the feature

Following actions were taken to ensure familiarity:

  • Ensure documentation provides clear explanation on configuration options
  • Ensure good user experience and simplicity of use

Advanced topics for test development

  • Interacting with a serverless application using HTTP2 and gRPC
  • Quarkus function deployment using 'kn func' plugin
  • Quarkus function deployment using OpenShift CLI (oc) and YAML templates

Contacts

References