Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build and deploy Dagster AMI #924

Merged
merged 9 commits into from
Jul 12, 2022
Merged

Build and deploy Dagster AMI #924

merged 9 commits into from
Jul 12, 2022

Conversation

blarghmatey
Copy link
Member

@blarghmatey blarghmatey commented Jun 29, 2022

Updated the Dagster deployment to pre-bake an AMI and deploy using docker containers

Description

This adds code for building an AMI to run the Dagster data orchestrator using the containers being created as part of mitodl/ol-data-platform#240 and updates the Pulumi code to use that new image for deployment

Motivation and Context

This is related to mitodl/ol-data-platform#233

How Has This Been Tested?

The built image has been deployed and validated that the UI is accessible and pipelines render properly.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Enhancement (improves on existing behavior)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project. (Did you install and run the pre-commit hooks?)
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Closed #900

@blarghmatey blarghmatey requested a review from shaidar June 29, 2022 21:10
@blarghmatey blarghmatey self-assigned this Jun 29, 2022
@blarghmatey blarghmatey changed the title Md/issue 900 Build and deploy Dagster AMI Jun 30, 2022
Created docker-compose and .env templates/files for running dagster in containers.

Created a DAGSTER_VERSION default.

Created testing infrastructure for running dagster+docker-compose along side a traditional dagster deployment without being disruptive.

Created a dagster ami based on the docker-baseline.

Created an ugly non-minimal vault policy for dagster docker-compose servers.

Adding a missing environment variable to the dagster .env template file.

Added nginx with basic auth infront of dagster.

fix: Resolve basic auth and env issues with Dagster

- The basic auth config for Dagster was not using a properly formatted htpasswd file
- Add explicit reference to the env file for dagit/dagster-daemon in the docker-compose file

Paramtizer the dagster bucket value that will be shared with dagster.yaml. Squashed a few bugs.

Updated the version of dagster.

Removed the legacy salt-stack code from the dagster stacks.

Adding the .env file to the edx-pipeline.

Tweaking the dagster stack to use fewer security groups and be a bit neater.

Fixed a templating problem with the xpro pipeline.

Fixed another templating problem with the xpro pipeline.

Fixed a few copy and paste errors with the mitxonline template.

Created production configuration for dagster and fixed a few changed stack keys in the consul data.
@Ardiea Ardiea marked this pull request as ready for review July 8, 2022 16:38
@Ardiea Ardiea mentioned this pull request Jul 11, 2022
3 tasks
@blarghmatey
Copy link
Member Author

👍

@Ardiea Ardiea merged commit 3fb3f86 into main Jul 12, 2022
@Ardiea Ardiea deleted the md/issue_900 branch July 12, 2022 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dagster AMI build and envrionment deployment
2 participants