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

As a DS I would like to auto schedule regular training/packaging/deployment for models for which I have already manually run training, packaging & deployment #642

Open
alinaignatiuk opened this issue Dec 17, 2021 · 0 comments
Labels
feature [Added] for new features. major without one user can perform the target action in a workaround, but it's not obvious WPM

Comments

@alinaignatiuk
Copy link

alinaignatiuk commented Dec 17, 2021

Business context: Once the data scientist has determined the best model, trained, packaged and deployed on ODAHU k8s cluster this model is going to be used by external services. However, over time the data updates are coming and the model should be retrained periodically with respect to the new data sets. In most cases nothing should change except new cases appear in the data sets. Based on this the model should be retrained, repackaged and redeployed to provide more accurate predictions and results based on the latest data.

Use case: Auto scheduling for training/packaging/deployment

Design: ODAHU UI (feature available over ODAHU UI)

Acceptance criteria:

  1. User should be able to activate auto scheduler for models which have been already manually trained, packaged and deployed in ODAHU
  2. User should indicate
  • trained model ID,
  • packaged model ID,
  • deployed model ID and
  • auto scheduler parameters
  1. Auto scheduler parameters:
  • on/off
  • start date (mandatory)
  • end date (optional, if not indicated, then it will run forever)
  • start time (mandatory)
  • frequency (daily, weekly, bi-weekly, monthly)
  • day(s) of the week
  • time zone (time as per local time zone, converted to UTC) - informational field
  1. User should be able to pick up the trainer model ID, packaged model ID and deployed model IDs from the lists
  2. User should be able to see the list of auto scheduled models with current status On/Off/Running(?)
  3. For each run of auto scheduled training, packaging and deployment the system should save information into the registry to
    about auto scheduled models training, packaging and deployment runs (discuss)

Dependency:

  1. Within the training, packaging and deployment model lists would be good to recognize those models that have auto scheduler active

Decomposition:
We need to provide rough estimate and order of the tasks

ODAHU UI:

  1. Auto scheduled models list
  2. Scheduler parameters form
  3. Update training, packaging & deployment lists respectively for AC.6

ODAHU back-end:

  1. Create BD
  2. Create API
  3. Create separate entity for Scheduler
  4. Run the model training as per the existing parameters and data for this particular model ID
  5. Update training artifact in the packaging input parameters
  6. Update packaging artifact in the deployment input parameters
  7. Create logic
  8. Check whether we have functions which create Trained, Packaged and Deployed models IDs lists (3 lists)
@alinaignatiuk alinaignatiuk created this issue from a note in odahu-kanban (To Do) Dec 17, 2021
@alinaignatiuk alinaignatiuk added 1.7 feature [Added] for new features. WPM major without one user can perform the target action in a workaround, but it's not obvious labels Dec 17, 2021
@alinaignatiuk alinaignatiuk moved this from To Do to Backlog in odahu-kanban Jan 11, 2022
@alinaignatiuk alinaignatiuk removed the 1.7 label Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature [Added] for new features. major without one user can perform the target action in a workaround, but it's not obvious WPM
Projects
odahu-kanban
  
Backlog
Development

No branches or pull requests

1 participant