Community extensions

This release includes multiple CK extensions based on the user feedback:

• added --j flag to "ck install package" to update CK_HOST_CPU_NUMBER_OF_PROCESSORS env and force number of processes in "make -j" if used by a given package
• added ck.cfg key "pip_user". If yes, add --user when to pip when installing CK repositories.
  Turn it on as follows:
  $ ck set kernel var.pip_user=yes
  See ticket #157
• print path to the CK kernel when invoking "ck"
• extended "result" module to use meta.json as a base for all sub configurations (to simplify configuration for multiple dashboards - useful for MLPerf)

support for the new CK dashboards and other improvements

• added result.cfg to configure CK dashboards
• improved module:result to push results to CK dashboards
• improved module:dashboard to work with new CK dashboards
• improved module:wfe to work with new CK dashboards
• added module:ck-platform to work with cKnowledge.io platform (moved cbench functionality from the CK incubator to the CK module to work with cKnowledge.io dashboards directly)
• provided better support to work with CK modules as standard Python packages (see module:ck-platform as example)

regular extensions based on user feedback

• added support to automatically add simple packages from Git:

   ck add package:my-git-repo --git={URL} --tags=my-repo --env_ext=MY_GIT_REPO

• added module:mlperf.result to abstract official MLPerf results
• added key "skip_global_deps" to program meta to skip global dependencies
  for a given command line (for example, only to install python deps
  for a given program)
• improved handling of a situation when CK environment has changed
  and make it possible to continue running a workflow at user risk
  (useful for debugging)

various extensions

• added "pull" function to module:docker
• if only 1 tag exists in Docker, select it automatically
• updated docs
• fixed ck run docker --command="something" on Linux
• added --min_run to module:program to avoid pre/post processing and just run a command.
  Useful to install Python requirements for a given program CMD.
  We use it in MLPerf automation.

automatically installing Python requirements from pulled repos

• auto-install Python requirements from pulled repositories
• added --bash to docker:module to run bash in a container
• removed outdated and unnecessary files
• added --command flag to "run docker" to run a specific command such as ck run docker:xyz --command="ck show env"

many enhancements to handle adaptive Docker containers via CK

• added module "docker.template" to support adaptive CK containers
• added rebuild function to module:docker to rebuild images (#145)
• added support for multiple Docker tags in module:docker . See example: https://github.com/octoml/mlops/tree/main/docker/ck-template-mlperf
• added "default_org" key in a CK Docker entry meta to specify default organization
• added "outdated" and "aging" keys in Docker images to warn user about the status of a given Docker container
• added main CK and MLPerf repositories to Zenodo to ensure reproducibilty
• added common function "tested" to mark CK entries as tested, i.e. "ck tested docker:mlperf-inference-v0.7.openvino"

"ck search" improvement for entries with inheritance

• improved "ck search" to search tags in entries with inheritance
• fixed function "ck status"

enhancement of the inheritance mechanism and a few bug fixes

We keep original meta of a given entry when updating, copying or moving it rather than expanding it with all the base entries.W

basic support for inheritance of CK entries

• added support for basic inheritance in CK entries via "_base_entry" key. Useful to simplify program, package and soft modules. See ticket #143.
• added program.template, soft.template and package.template modules to describe base entries for inheritance.

added missing requirements.txt to the main distro

V2.0.9

added missing requirements.txt to the distro