otter-service-stdalone 1.1.38

Grading Service for Instructors using Otter Grader

otter-service-standalone

Use: Instructions

Deployment

The cloud deployment is configured using a helm chart. The branch you are on(e.g. dev, staging, prod) determines what environment/k8 namespace you deploy into.

See the ./deploy.sh for details. The script will determine the branch and deploy properly. If you are on the dev branch and pass "build" as an argument, (e.g. ./deploy.sh build) then the docker image used on the container is built and pushed to the gcloud image repository (gcr.io). You need to be sure to bump the version number in src/otter_service_stdalone/init.py before a new build.

To deploy to a different Kubernetes cluster, pass an explicit kube context instead of relying on your current default context. The script will first run kubectl config use-context and then use that same context for kubectl and helm:

./deploy.sh --context my-other-cluster-context

You can also override the namespace or Helm release name when needed:

./deploy.sh --context my-other-cluster-context --namespace otter-stdalone-prod --release otter-srv

You can layer a Helm override file on top of the normal branch values:

./deploy.sh --context my-other-cluster-context --values-file my-values-override.yaml

The same values can be provided via environment variables:

KUBE_CONTEXT=my-other-cluster-context KUBE_NAMESPACE=otter-stdalone-prod HELM_EXTRA_VALUES_FILE=my-values-override.yaml ./deploy.sh

Cluster Migration

Internal migration runbook content has moved to migration.md at the repository root.

Version

A git tag with the version is pushed to git whenever the version is bumped and deployed in production. git tag will show you the format of the tag(e.g. 0.0.30)

Local Dev:

Execute: sh deployment/local/build.sh

• FireStore: http://127.0.0.1:4007/firestore/
• App: http://127.0.0.1/