Skip to content

Releases: compute-tooling/compute-studio

Compute Studio 1.9

Choose a tag to compare

@hdoupe hdoupe released this 18 May 01:12
3694640
  • Remove final scaling barriers for adding new job-based (i.e. uses paramtools) projects to C/S.
  • Use queue based model for processing outputs from jobs/simulations.
  • Use Postgres backed storage system for the compute cluster with the SQLAlchemy ORM and FastAPI api framework.
  • Use Kubernetes namespaces to better lock down network access between services.

For more info, check out the write up in PR #412.

Compute Studio 1.8.0

Choose a tag to compare

@hdoupe hdoupe released this 14 Dec 23:28
21799e5
  • Simplified and streamlined app publishing process.
  • Private apps that are only available to you and your team.
  • Simulations are public by default.
  • Infrastructure updates producing a snappier site, silky-smooth releases, and support for running your own C/S compute cluster.
  • Revamped C/S Pro subscription for unlimited private simulations and private apps at $9/month.

Compute Studio 1.7.0

Choose a tag to compare

@hdoupe hdoupe released this 14 Sep 12:19
656c4f8
  • Adds ability to host interactive visualizations that use Dash, Bokeh, or other dynamic visualization software. (#308)

Screenshot from 2020-09-14 08-18-34

  • Add support for two-dimensional array fields. (#289)

Screenshot from 2020-09-14 08-16-25

  • Make storage bucket for results from simulations private to prevent access to results from private simulations. (#305)

  • Inject app secrets as environment variables when running app tests. (#303)

Compute Studio 1.6.1

Choose a tag to compare

@hdoupe hdoupe released this 29 May 15:23
41b89e6
  • Improve worker cluster configuration. (#286)
  • Add service to clean up resources from successful simulations. (#286)

Compute Studio 1.6.0

Choose a tag to compare

@hdoupe hdoupe released this 27 May 19:00
4ee4a42
  • Close-to-automatic updates and deploys. When a user creates or updates a model on the publish page, I get an email notification. Using the cs-publish package, I kick off a GH actions work flow:

    cs-publish -n [:owner]/[:title]
    

    I can then deploy the update/new model by merging the PR.

  • Simulations are run as Kuberenetes Jobs. This means that models no longer have to have at least one process running all of the time, and thus reducing C/S compute cost. One side-effect of doing this is that we no longer have Celery's constraint of only being allowed to use one process per worker.
    Screenshot from 2020-05-25 16-09-32

  • Secrets are now stored in Google Secret Manger or any other secret manager backend. This improves C/S security and makes it possible for modeler's to manage their own secrets from the webapp or rest api. This is similar to how GH lets you manage secrets for your Repository.

  • The workers have a new CLI tool to manage this:

export TAG=mytag CS_URL=https://compute.studio CS_API_TOKEN=secret PROJECT=gcp-project-name

# Update c/s api:
csw svc build
csw svc push
csw svc config -o - | kubectl apply -f -

# Update, get, delete c/s secrets
csw svc secrets set --secret-name CS_API_TOKEN --secret-value $CS_API_TOKEN
csw svc secrets get CS_API_TOKEN
csw svc secrets delete CS_API_TOKEN

# Update c/s model
csw models -n PSLmodels/Tax-Cruncher build
csw models -n PSLmodels/Tax-Cruncher test
csw models -n PSLmodels/Tax-Cruncher push

# Set staging tag
csw models -n PSLmodels/Tax-Cruncher stage $TAG

# Deploy and promote latest tag
csw models -n PSLmodels/Tax-Cruncher config -o - | kubectl apply -f - 
csw models -n PSLmodels/Tax-Cruncher promote

# Update, get, list, delete c/s model secrets
csw models -n PSLmodels/Tax-Cruncher secrets set --secret-name super --secret-value secret
csw models -n PSLmodels/Tax-Cruncher secrets get super
csw models -n PSLmodels/Tax-Cruncher secrets list
csw models -n PSLmodels/Tax-Cruncher secrets delete super
  • Also, the flask server has been re-written as a tornado app. This is advantageous because it's main job is to receive and submit requests. Async servers do very well with this type of work.

  • All model configuration data is now stored in the webapp. Modelers can update their repo url, repo tag, memory, and cpu requirements directly from the webapp. The build system will pull the values from the /publish/api/ endpoint.

Compute Studio 1.5.0

Choose a tag to compare

@hdoupe hdoupe released this 08 Apr 16:09
0304cfa

Compute Studio 1.4.2

Choose a tag to compare

@hdoupe hdoupe released this 07 Apr 14:51
e2cc902
  • Bug fix for case where a meta parameter's value evaluates as false. This fix checks if the value property exists on the object instead of whether it exists and is false-y.

Compute Studio 1.4.1

Choose a tag to compare

@hdoupe hdoupe released this 07 Apr 14:39
0621531
  • Bug fix for loading the new format of meta parameters values. (#278)

Compute Studio 1.4.0

Choose a tag to compare

@hdoupe hdoupe released this 07 Apr 13:48
48f4176
  • Save model inputs to reduce page load times and to make it possible to fully-archive model simulations without having to worry about model's making backwards-incompatible changes to their inputs. (#277)

Compute Studio 1.3.1

Choose a tag to compare

@hdoupe hdoupe released this 24 Mar 14:17
0e952c4
  • Fix Bokeh 2.0.0 compatibility issue. (#276)
  • Fix invoice totals by scaling by 100. (#274)
  • Includes more email address swaps. (#275)