search

ioos / governance

Processes and procedures for management of the U.S. IOOS GitHub Organization (https://github.com/ioos)
Creative Commons Zero v1.0 Universal
0 stars 3 forks source link

ioos-sagemaker-deploy #12

Open mykelalvis opened 1 week ago

mykelalvis commented 1 week ago

Repository name

ioos-sagemaker-deploy

Repository purpose

Perform deployments of sagemaker for IOOS

Repository description

Terraform to be applied to perform deployments for sagemaker.

Repository type

Public

Repository license

BSD 3-Clause

Repository options

Specify a .gitignore file type

No response

Specify GitHub usernames or IOOS GitHub Team for repository access

ioos/modeling Maintain

MathewBiddle commented 1 week ago

Thank you for this request @mykelalvis! I'm curious how this might relate to https://github.com/ioos/cloud-sandbox-sagemaker. Can you provide some insight?

mykelalvis commented 1 week ago

cloud-sandbox-sagemaker (to be renamed) produces a custom image for an ioos ipykernel image for sagemaker. UPDATE FOR CLARIFICATION: This repo that I am requesting with issue #12 (this issue) should produce custom modules, released only when needed. There should be a third to produce a deploy-on-merge application combining those things for easy of change-management.

The granularity of the release cycles of the three things are (hopefully) very different, so they shouldn't live together. If I'm being honest, there should be a repo-per-module for terraform, but I think the release cycle on that should be "almost-never" once it settles down. The image and the actual deployment will change fairly frequently, although not on the same cycle.

mykelalvis commented 1 week ago

BTW, these can be private if that helps with reporting issues.

mwengren commented 1 week ago

Based on discussions with @mykelalvis this morning, I recommend we make this '-deploy' repo private, and the other should be public. For ease of management, we will need all three, however.

We can rename them all to follow a naming scheme to help distinguish between the 2 (or 3), and also to associate them all as connected to the existing 'ioos/Cloud-Sandbox' main repo, ideally. I'd like to follow the 'cloud-sandbox-' prefix for a naming scheme for all of them.