-
Notifications
You must be signed in to change notification settings - Fork 14
Standalone CLI: sub #232
Standalone CLI: sub #232
Conversation
docs/cli.md
Outdated
## List | ||
|
||
```bash | ||
strat ls (list) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to strat
, -1 to ai
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think sub
has my preference right now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sub it is!
install/gcp/up.sh
Outdated
--max-cpu 960 --max-memory 9600 --ephemeral-storage-local-ssd=count=2 \ | ||
--autoprovisioning-scopes=logging.write,monitoring,devstorage.read_only,compute \ | ||
--addons GcsFuseCsiDriver | ||
gcloud container clusters create ${CLUSTER_NAME} --location ${REGION} \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this messes up the docs rendering so would prefer original formatting instead of spaces at beginning of lines
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Editor side-effect, reverted
Overall the CLI looks promising! Can't wait to try it out for my dev flow. I would prefer to keep this PR only to what's needed to make the Standalone CLI work. Any refactors should be done as separate PRs and discussed separately. Things like reformatting the gcp install scripts or renaming |
docs/container-contract.md
Outdated
data/ # Location where Datasets will be mounted (reading and loading). | ||
data/ # Location where a previously stored Datasets is mounted. | ||
model/ # Location where a previously stored Model is mounted. | ||
output/ # Location to store output of a run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change to `artifacts
@@ -127,7 +125,6 @@ The example Model's backing storage would end up being: | |||
|
|||
```sh | |||
gs://abc123-substratus-artifacts/f94a0d128bcbd9c1b824e9e5572baf86/model/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is no longer a good reason to store model in a subdirectory
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed, I think this doc is wrong now, will fix
install/gcp/up.sh
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please revert all changes in this file unless these changes were needed to fix something
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will do before merge
Edit: Ignore this is already fixed in commit 47c4a76 I noticed the following log:
|
Not for this PR, but something to discuss as a follow up. One thing that was rather annoying was being unable to edit params.json from within the notebook. It's mounted as read-only. I noticed I had a typo in my param.json and my only way to solve it was to delete the notebook and modify the substratus resource. |
file syncing currently only happens for files in |
## Substratus.yaml | ||
|
||
### Option 1: Workspace file | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
workspace file seems complex, having multiple files feels cleaner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed
|
||
**Cons:** | ||
|
||
* Could get messy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and complex if you never used kustomize
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed
# Generated if not specified | ||
``` | ||
|
||
### Option 2: Multi-doc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this or simply creating multiple files within same dir is better
w.Add("/content/src") | ||
const contentDir = "/content" | ||
|
||
// NOTE: Watch is non-recursive. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so it would watch /content/src
but not /content/src/my-dir/sam.ipynb
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep
Mounts: []cloud.BucketMount{ | ||
{BucketSubdir: "data", ContentSubdir: "data"}, | ||
{BucketSubdir: "logs", ContentSubdir: "logs"}, | ||
{BucketSubdir: "artifacts", ContentSubdir: "artifacts"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need a BucketSubdir
now that it is all artifacts together? I think probably cleaner to remove it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont think we need it anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will leave for later refactor
internal/cli/push.go
Outdated
} | ||
|
||
cmd := &cobra.Command{ | ||
Use: "push [dir]", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with push
as well but feel run
is more descriptive of what the end-result is here. The pushing is just an intermediary step to run it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to run
Tracking the param.json issue here: #237 |
Add a standalone CLI:
sub
Replaces the current kubectl plugins.