awslabs/benchmark-ai

[SM-Executor/Watcher] Benchmark job id

Open

#941 opened on Oct 14, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (6 forks)auto 404
enhancementgood first issueservice:sm-executorservice:watcher

Repository metrics

Stars
 (19 stars)
PR merge metrics
 (PR metrics pending)

Description

For kubernetes jobs, the job id is in the format b-<action-id>, where as for sage maker jobs, the job ids are in the format <action-id>. We should update the sm-executor (and also the watcher) to observe the naming convention for benchmark jobs (i.e. b-<action-id>)

Contributor guide

Research direction
Locate where job IDs are generated in the sm executor and watcher code, then add 'b ' prefix for benchmark jobs.
Tech stack
python
Domain
backendinfrastructure
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90