Uploaded image for project: 'OpenShift Node'
  1. OpenShift Node
  2. OCPNODE-806

Dev preview of Crun in openshift

    XMLWordPrintable

Details

    • Epic
    • Resolution: Done
    • Normal
    • openshift-4.11
    • None
    • None
    • Dev preview of Crun in openshift
    • True
    • This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic.
    • False
    • Green
    • To Do
    • Impediment
    • 100
    • 100% 100%

    Description

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • ...

      Why is this important?

      • While most of the tools used in the Linux containers ecosystem are written in Go, I believe C is a better fit for a lower level tool like a container runtime. runc, the most used implementation of the OCI runtime specs written in Go, re-execs itself and use a module written in C for setting up the environment before the container process starts.

      crun aims to be also usable as a library that can be easily included in programs without requiring an external process for managing OCI containers.

      • crun is faster than runc and has a much lower memory footprint.

      This is the elapsed time on my machine for running sequentially 100 containers, the containers run /bin/true:

        crun runc %
      100 /bin/true 0:01.69 0:3.34 -49.4%

      https://github.com/containers/crun 

      Scenarios

      1. ...

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

      Attachments

        Issue Links

          Activity

            People

              rphillip@redhat.com Ryan Phillips
              gausingh@redhat.com Gaurav Singh
              Pravin Mali Pravin Mali (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: