This repository contains the deployment files and instructions for installing the Simulation Toolkit For Scientific Discovery (ST4SD).
We currently support installing the ST4SD stack via helm.
- Access to an OpenShift cluster with
cluster-adminpermissions- Required for creation of a kubernetes objects (such as CustomResourceDefinition and Role Based Access Control (RBAC)). Regular updates to the workflow stack do not require
cluster-adminpermissions, only permissions to modify objects in the namespace that holds the workflow stack.
- Required for creation of a kubernetes objects (such as CustomResourceDefinition and Role Based Access Control (RBAC)). Regular updates to the workflow stack do not require
- OpenShift command line tools (
ocv4.9+)- Instructions: https://docs.openshift.com/container-platform/4.9/cli_reference/openshift_cli/getting-started-cli.html
- Install stable version of
ocfrom https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/ - It is good practice to periodically update your
occommand line utility to ensure that yourocbinary contains the latest patches and bug-fixes.
Coming soon.
Please feel free to reach out to one of the maintainers listed in the MAINTAINERS.md page.
We always welcome external contributions. Please see our guidance for details on how to do so.
If you use ST4SD in your projects, please consider citing the following:
@software{st4sd_2022,
author = {Johnston, Michael A. and Vassiliadis, Vassilis and Pomponio, Alessandro and Pyzer-Knapp, Edward},
license = {Apache-2.0},
month = {12},
title = {{Simulation Toolkit for Scientific Discovery}},
url = {https://github.com/st4sd/st4sd-runtime-core},
year = {2022}
}This project is licensed under the Apache 2.0 license. Please see details here.
- Take a look at the troubleshooting-deployment guide to ensure that your workflow stack is properly instantiated.
- Get started with ST4SD.
- Test your ST4SD deployment using the st4sd-examples notebooks.
- Visit the ST4SD runtime service: at
${routePrefix}.{clusterRouteDomain}/rsNote: Replace
${key}with the value ofkeyin yourdeployment-options.yamlfile (the one that you created when following the requirements instructions).