Uploaded image for project: 'JBeret'
  1. JBeret
  2. JBERET-349

Integrate JBeret with openshift scheduled job capability

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • None
    • 1.3.0.Beta6
    • jberet-openshift
    • None

    Description

      A scheduled job builds on a regular job by allowing you to specifically schedule how the job should be run. Scheduled jobs are part of the Kubernetes API, which can be managed with oc commands like other object types.

      As of OpenShift Container Platform 3.3.1, Scheduled Jobs is a feature in Technology Preview.

      https://docs.openshift.com/container-platform/3.10/dev_guide/cron_jobs.html

      https://docs.openshift.com/container-platform/3.10/dev_guide/jobs.html

      https://docs.openshift.com/online/dev_guide/jobs.html

      S2I images for Java application:
      https://docs.openshift.com/online/using_images/s2i_images/java.html

      A short blog post on OpenShift jobs:
      https://blog.openshift.com/openshift-jobs/

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JBERET-449 Support batch job execution with OpenShift cron job scheduling mechanism

          • 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.
          • Coding In Progress

          Task - Represents a small unit of work that is not end-user facing. JBERET-450 Launch and schedule batch job executions on OpenShift Thorntail runtime with Kubernetes jobs api

          • 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.
          • Coding In Progress
          relates to

          Task - Represents a small unit of work that is not end-user facing. JBERET-448 Move test-apps/simple to its own repo

          • 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
          links to

          Web Link Github Repo

          Activity

            People

              weinanli Weinan Li
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: