[FEATURE]: Fix Trainspace POST endpoints to support new Training Flow

[dwu359]

Feature Name

Fix Trainspace POST endpoints to allow to support new Training Flow

Your Name

Daniel Wu

Description

Problem When a trainspace is currently created, it is separated by steps and categories rather than by blocks.

Approach We want modify the trainspace POST endpoints to store the following in a trainspace table in dynamo:

• id
• date created
• user id
• list of datasets
• list of models
• list of blocks

Dataset:

• Source (default, s3)
• dataset id
• s3 url (if s3 source)

Models:

• Name
• Model id
• Dataset id
• list of model versions:
• Model versions:
  • Name of model version
  • s3 url to model

Blocks (stored within trainspace item):

• Block id
• Type of block
• Other info based on the type of block
• Run data
  • s3 url, string, number, etc based on the type of block

Any other considerations The trainspace POST endpoints currently run serverlessly and are written as Infra as Code through SST.

[github-actions[bot]]

Hello @dwu359! Thank you for submitting the Feature Request Form. We appreciate your contribution. :wave:

We will look into it and provide a response as soon as possible.

To work on this feature request, you can follow these branch setup instructions:

1. Checkout the main branch:

    git checkout nextjs

2. Pull the latest changes from the remote main branch:

    git pull origin nextjs

3. Create a new branch specific to this feature request using the issue number:

    git checkout -b feature-1073

   Feel free to make the necessary changes in this branch and submit a pull request when you're ready.

   Best regards, Deep Learning Playground (DLP) Team

[karkir0003]

whats the purpose of blocks table @dwu359