d3x Commands¶
d3x commands are used for managing the user workspace, apikeys, ray clusters, user apps and deployments. This page provides information about all of the d3x commands that are currently available, along with their functions, usage syntax and available options.
Usage¶
d3x [OPTIONS] COMMAND [ARGS]...
d3x --help
Function¶
Group for d3x commands.
Options¶
Option |
Description |
|---|---|
|
Enable requests debugging. |
|
Cluster profile. |
|
Show help for the command. |
Commands¶
Command |
Description |
|---|---|
|
Details about DKubeX CLI config |
|
Commands to generate and get DKubeX API keys. |
|
Commands regarding creating and managing user-defined applications. |
|
Commands for backing up datasets. |
|
Commands for creating, managing and using datasets. |
|
Commands regarding using embedding models. |
|
Commands regarding using foundation models. |
|
LLM Finetuning process related commands. |
|
List available instance types. |
|
Commands regarding using LLMs. |
|
Login to DKubeX with particular user profile in the CLI. |
|
Commands for using and managing experiments and models in MLFlow from CLI. |
|
Mount S3 bucket in read/write mode. |
|
Commands regarding user profiles in DKubeX. |
|
Commands for generating questions and answers. |
|
Commands regarding Ray jobs and Ray clusters. |
|
Commands for restoring databases. |
|
Commands for creating model deployments. |
|
Commands for managing SkyPilot clusters, resources and jobs. |
|
Unmount bucket previously mounted using |
|
Show DKubeX version. |
|
Commands for managing workspaces and workspace applications. |
d3x about¶
Usage
d3x about [OPTIONS]d3x about --helpFunction
Details about DKubeX CLI config
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command.
d3x apikey¶
Usage
d3x apikey [OPTIONS] COMMAND [ARGS]...d3x apikey --helpFunction
Commands to generate and get DKubeX API keys.
Options
Option
Description
--helpShow help for the command.
Commands
Command
Description
generateGenerate new API key for the user.
getGet currect API key for the user.
Usage
d3x apikey generate [OPTIONS]d3x apikey generate --helpFunction
Generate new API key for the user.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command.
Usage
d3x apikey get [OPTIONS]d3x apikey get --helpFunction
Get current API key for the user.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for this command.
d3x apps¶
Usage
d3x apps [OPTIONS] COMMAND [ARGS]...d3x apps --helpFunction
Commands regarding creating and managing user-defined applications.
Options
Option
Description
--helpShow help for this command.
Commands
Command
Description
createDeploy the user-defined application on DKubeX.
deleteDelete user apps.
listList user apps.
openOpen user app in browser.
startStart user apps.
stopStop user apps.
Usage
d3x apps create [OPTIONS] [COMMAND]...d3x apps create --helpFunction
Deploy the user-defined application on DKubeX.
Options
Option
Description
-c,--config TEXTPath to the .yaml configuration file
--helpShow help for this command.
Usage
d3x apps delete [OPTIONS] NAMEd3x apps delete --helpFunction
Delete user apps
Options
Option
Description
-u,--user TEXTName of user by whom the app is published.
-p,--publishedTo publish an deployed user app.
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for this command.
Usage
d3x apps list [OPTIONS]d3x apps list --helpFunction
List user apps.
Options
Option
Description
-a,--allList user apps including shared users.
-o,--output [yaml|json]Outupt format (supported- .json, .yaml)
--helpShow help for this command.
Usage
d3x apps open [OPTIONS] NAMEd3x apps open --helpFunction
Open user app in browser.
Options
Option
Description
-u,--user TEXTapp’s owner name
-p,--publishedpublished userapp
--helpShow this message and exit.
Usage
d3x apps start [OPTIONS] NAMEd3x apps start --helpFunction
start user apps
Options
Option
Description
-u,--user TEXTapp’s owner name
-p,--publishedpublished userapp
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow this message and exit.
Usage
d3x apps stop [OPTIONS] NAMEd3x apps stop --helpFunction
stop user apps
Options
Option
Description
-u,--user TEXTapp’s owner name
-p,--publishedpublished userapp
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow this message and exit.
d3x backup¶
Usage
d3x backup [OPTIONS] COMMAND [ARGS]...d3x backup --helpFunction
Commands for backing up datasets.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
weaviatecommand for weaviate backup
Usage
d3x backup weaviate [OPTIONS]d3x backup weaviate --helpFunction
Command for dataset backup to Weaviate.
Options
Option
Description
-d,--dataset TEXTA name to represent the ingested docs [required]
-i,--id TEXTAn ID for the backup [required]
-b,--backend [filesystem|s3]s3 or filesystem to save the backup [required]
--helpShow help for the command.
d3x dataset¶
Usage
d3x dataset [OPTIONS] COMMAND [ARGS]...d3x dataset --helpFunction
Commands for creating, managing and using datasets.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
deleteDeletes specified dataset if present from the database
evaluateRun evaluation pipeline over the given dataset.
ingestIngest the documents from provided source into the database.
listlists all the datasets present in database
queryQuery over documents using the selected pipeline.
showshows documents present in the specified dataset
Usage
d3x dataset delete [OPTIONS] DATASETd3x dataset delete --helpFunction
Deletes specified dataset if present from the database.
Options
Option
Description
--helpShow help for the command..
Usage
d3x dataset evaluate [OPTIONS]d3x dataset evaluate --helpFunction
Option
Description
-d,--dataset TEXTDataset on which the queries should be applied. [required]
-p,--pipeline TEXTRAG pipeline to be used.
-c,--config TEXTUser configuration for pipeline stages
-s,--remote-skyIf the ingestion should be scheduled on remote sky cluster.
-m,--remote-command TEXTsky/ray job command to run.
-r,--remote-rayIf the ingestion should be scheduled on remote ray cluster.
-rc,--ray-config TEXTConfiguration for running remote ray job in json format
--dkubex-url TEXTURL of the dkubex for the remote clusters to reach.
-k,--dkubex-apikey TEXTAPI key for remote clusters to reach dkubex.
--helpShow help for the command..
Usage
d3x dataset ingest [OPTIONS]d3x dataset ingest --helpFunction
Ingest the documents from provided source into the vectorstore identified by given dataset name.
Note
SUPPORTED EXTRA OPTIONS: Make use of the options below to overwrite the individual values without need to copy config file.
--embedder.class=[HuggingfaceEmbedding/OpenAIEmbedding] --embedder.model=<embedding-model-name-for-the-above-class>
Options
Option
Description
-d,--dataset TEXTA name to represent the ingested docs [required]
-p,--pipeline TEXTIngestion pipeline to be used.
-c,--config TEXTUser configuration for pipeline stages
-s,--remote-skyIf the ingestion should be scheduled on remote sky cluster.
-r,--remote-rayIf the ingestion should be scheduled on remote ray cluster.
-rc,--ray-config TEXTConfiguration for running remote ray job in json format
-m,--remote-command TEXTSky/Ray job command to run.
--dkubex-url TEXTURL of DKubeX for the remote clusters to reach.
-k,--dkubex-apikey TEXTAPI key for remote clusters to reach DKubeX.
-w,--num-workers INTEGERNumber of process to use for parallelization.
--type TEXTNode selector.
--ngpus INTEGERNumber of gpus in case of gpu node type.
--faqOption to enable cache for the dataset.
--helpShow help for the command.
Usage
d3x dataset list [OPTIONS]d3x dataset list --helpFunction
Lists all the datasets present in database
Options
Option
Description
--helpShow help for the command..
Usage
d3x dataset query [OPTIONS]d3x dataset query --helpFunction
Query over documents using the selected pipeline.
Note
SUPPORTED EXTRA OPTIONS: Make use of the options below to overwrite the individual values without need to copy config file.
--vectorstore_retriever.embedding_class=[HuggingfaceEmbedding/OpenAIEmbedding] --vectorstore_retriever.embedding_model= --vectorstore_retriever.top_k= --chat_engine.llm=[openai/dkubex] --chat_engine.url=<dkubex-dep-url> --chat_engine.llmkey=<llm-access-key> --chat_engine.max_tokens
Options
Option
Description
-d,--dataset TEXTDataset on which the question should be applied. [required]
-p,--pipeline TEXTRAG pipeline to be used.
-c,--config TEXTUser configuration for pipeline stages
-q,--question TEXTUser query to run through the pipeline
-b,--batch TEXTBatch of questions to run through the pipeline
-i,--interactiveRun this tool in cli mode
-f,--filters TEXTChunk-Metadata filter expression in string format
-k,--conversation TEXTName of the conversation to track all the questions for.
--helpShow help for the command..
Usage
d3x dataset show [OPTIONS]d3x dataset show --helpFunction
Shows documents present in the specified dataset
Options
Option
Description
-d,--dataset TEXTDataset name to list all the docs present in it [required]
--helpShow help for the command.
d3x emb¶
Usage
d3x emb [OPTIONS] COMMAND [ARGS]...d3x emb --helpFunction
Commads regarding using embedding models.
Options
Option
Description
--helpShow help for the command.
Commands
Command
Description
deployCommand to deploy an embedding model.
listList the supported embedding models on DKubeX.
Usage
d3x emb deploy [OPTIONS]d3x emb deploy --helpFunction
Command to deploy an embedding model.
Options
Option
Description
-n,--name TEXTname of the deployment [required]
-m,--model TEXTname or path of the model to deploy for embeddings
--base_model TEXTbase model name
--token TEXThugging face token
--config TEXTgithub raw content url or local config path
--mlflow TEXTname of the mlflow registered model along with version (example:
diffusion:1)--image TEXTcustomized docker image for llm deployment
--type TEXTinstance type
--min_replicas TEXTminimum replicas
--max_replicas TEXTmaximum replicas
--publishpublish the deployment
-o,--output [yaml|json]Output format (supported- .json, .yaml)
-sky,--remote-skyIf the model should be deployed on remote sky cluster.
--sky-accelerator TEXTaccelerator for remote sky cluster
--sky-yaml TEXTPath to custom yaml file for sky serve.
-skyk8s,--sky-k8sIf the model should be deployed on Kubernetes sky cluster.
--kserveWhether to use kserve for deployment.
--ngpus INTEGERNumber of GPUs to be used for deployment.
--helpShow help for the command.
Usage
d3x emb list [OPTIONS]d3x emb list --helpFunction
List the supported embedding models on DKubeX.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command.
d3x fm¶
Usage
d3x fm [OPTIONS] COMMAND [ARGS]...d3x fm --helpFunction
Commands regarding using foundation models.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
deleteDelete FM job.
getGet FM job details.
jobsList FM jobs.
logsShow logs of given FM job.
trainchunksCreate train and/or test chunks for finetuning.
Usage
d3x fm delete [OPTIONS] JOB_NAMEd3x fm delete --helpFunction
Delete FM job.
Options
Option
Description
--helpShow help for the command..
Usage
d3x fm get [OPTIONS] JOB_NAMEd3x fm get --helpFunction
Get FM job details.
Options
Option
Description
--helpShow help for the command..
Usage
d3x fm jobs [OPTIONS]d3x fm jobs --helpFunction
List FM jobs.
Options
Option
Description
--helpShow help for the command..
Usage
d3x fm logs [OPTIONS] JOB_NAMEd3x fm logs --helpFunction
Show logs of given FM job.
Options
Option
Description
--helpShow help for the command..
Usage
d3x fm trainchunks [OPTIONS]d3x fm trainchunks --helpFunction
Create train and/or test chunks for finetuning.
Options
Option
Description
-s,--source TEXTThe path where finetune chunks are sourced from [required]
-d,--destination TEXTThe path where chunks will be kept for training [required]
--split [train|test]specify train or test. Default: both
-p,--split-percent INTEGERspecify percentage of docs to go in train/test
-l,--lastpick documents from backwards
--helpShow help for the command.
d3x ft¶
Usage
d3x ft [OPTIONS] COMMAND [ARGS]...d3x ft --helpFunction
LLM Finetuning process related commands.
Options
Option
Description
--helpShow help for the command.
Commands
Command
Description
deleteDelete finetuning jobs
detailsFinetuning job details
finetuneFinetuning of model
get-configGet predefined finetuning config
jobsList finetuning jobs
list-configsList predefined finetuning configs
logsFinetuning job logs
mergeCreate finetuning job
quantizeCreate finetuning job
Usage
d3x ft delete [OPTIONS] NAMEd3x ft delete --helpFunction
delete finetuning jobs
Options
Option
Description
--helpShow help for the command.
Usage
d3x ft details [OPTIONS] NAMEd3x ft details --helpFunction
finetuning job details
Options
Option
Description
--helpShow help for the command.
Usage
d3x ft finetune [OPTIONS]d3x ft finetune --helpFunction
Command to finetune a model.
Options
Option
Description
-n,--name TEXTA name to represent the finetune job
-c,--config TEXTUser configuration for pipeline stages
-u,--dkubex-url TEXTURL of the dkubex for the remote clusters to reach.
--mlflow_experiment TEXTMLFlow experiment name for tracking
-k,--kind TEXTFinetuning type llm/flagemb/stemb/layoutllm [required]
-s,--remote-skyIf the Finetune should be scheduled on remote sky cluster.
-t,--type TEXTNode type in case of local finetune
-g,--gpu INTEGERNumber of gpus
-sc,--sky-cluster TEXTSky cluster name
-sa,--sky-accelerator TEXTSky cluster accelerator
-hft,--hf-token TEXTHuggingface token for downloading model
--dryrunOption for dry run
--helpShow help for the command.
Usage
d3x ft get-configd3x ft get-config --helpFunction
get predefined finetuning config
Options
Option
Description
-n,--name TEXTName of the config [required]
-k,--kind TEXTFinetuning type
llm/flagemb/stemb/layoutllm[required]--helpShow help for the command.
Usage
d3x ft jobs [OPTIONS]d3x ft jobs --helpFunction
list finetuning jobs
Options
Option
Description
--helpShow help for the command.
Usage
d3x ft list-configs [OPTIONS]d3x ft list-configs --helpFunction
list predefined finetuning configs
Options
Option
Description
-k,--kind TEXTFinetuning type
llm/flagemb/stemb/layoutllm[required]--helpShow help for the command.
Usage
d3x ft logs [OPTIONS] NAMEd3x ft logs --helpFunction
finetuning job logs
Options
Option
Description
--helpShow help for the command.
Usage
d3x ft merged3x ft merge --helpFunction
Command to merge finetuned models.
Options
Option
Description
-n,--name TEXTA name to represent the merge job [required]
-ft,--ft-name TEXTFinetuning job name
-o,--output-path TEXTAbsolute path to output directory. Defaults to the orginal checkpoint directory.
-cp,--checkpoint TEXTAbsolute path to checkpoint containing the LoRA weights.
-m,--model-name TEXTModel name(should contain complete hf path, e.g. meta-llama/Llama-2-13b-chat-hf)
--ray_cluster TEXTName of the ray cluster [required]
--ray_cluster_owner TEXTName of the ray cluster owner
--mlflow_runid TEXTMLFlow run id for the checkpoint
--mlflow_artifact TEXTMLFlow artifact path for checkpoint
-hft,--hf-token TEXTHuggingface token for downloading model
--dryrunOption for dry run
--helpShow help for the command.
Usage
d3x ft quantized3x ft quantize --helpFunction
Command to quantize finetuned models.
Options
Option
Description
-n,--name TEXTA name to represent the quantize job [required]
-ft,--ft-name TEXTFinetuning job name
-o,--output-path TEXTAbsolute path to output directory. Defaults to the orginal checkpoint directory.
-cp,--checkpoint TEXTAbsolute path to checkpoint containing the LoRA weights.
-m,--model-name TEXTModel name(should contain complete hf path, e.g. meta-llama/Llama-2-13b-chat-hf)
--ray_cluster TEXTName of the ray cluster [required]
--ray_cluster_owner TEXTname of the ray cluster owner
--mlflow_runid TEXTMLFlow run id for the checkpoint
--mlflow_artifact TEXTMLFlow artifact path for checkpoint
-hft,--hf-token TEXTHuggingface token for downloading model
--dryrunOption for dry run
--helpShow help for the command.
d3x instance-types¶
Usage
d3x instance-types [OPTIONS]d3x instance-types --helpFunction
List available instance types.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command.
d3x llms¶
Usage
d3x llms [OPTIONS] COMMAND [ARGS]...d3x llms --helpFunction
Commands regarding using LLMs.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
deployDeploy a LLM on dkubex.
listList the supported LLMs
Usage
d3x llms deploy [OPTIONS]d3x llms deploy --helpFunction
Deploy a LLM on dkubex.
Options
Option
Description
-n,--name TEXTName of the deployment [required]
-m,--model TEXTName or path of the model to deploy for serving
--base_model TEXTBase model name
--token TEXTHuggingface token
--config TEXTGithub raw content url or local config path
--mlflow TEXTName of the mlflow registered model along with version (example:
diffusion:1)--image TEXTCustomized docker image for llm deployment
--type TEXTInstance type/node selector
--min_replicas TEXTMinimum replicas
--max_replicas TEXTMaximum replicas
--publishPublish the deployment
-o,--output [yaml|json]Output format (supported- .json, .yaml)
-p,--provider TEXTProvider of llm [default is dkubex]
--ngc-api-key TEXTNGC API key for NIM provider
--qps TEXTQuestions per second for autoscaling
-sky,--skyIf the model should be deployed on remote sky cluster.
-skyk8s,--sky-k8sIf the model should be deployed on Kubernetes sky cluster.
--sky-accelerator TEXTaccelerator for remote sky cluster
--sky-yaml TEXTPath to custom yaml file for sky serve.
--use-spotWhether to request spot instances for sky deployments.
--kserveWhether to use the kserve for deployment.
--ngpus INTEGERNumber of GPUs
--helpShow help for the command..
Usage
d3x llms list [OPTIONS]d3x llms list --helpFunction
List the supported LLMs
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command.
d3x login¶
Usage
d3x login [OPTIONS]d3x login --helpFunction
Login to DKubeX with particular user profile in the CLI.
Options
Option
Description
--helpShow help for the command.
d3x mlflow¶
Usage
d3x mlflow [OPTIONS] COMMAND [ARGS]...d3x mlflow --helpFunction
Commands for using and managing experiments and models in MLFlow from CLI.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
experimentsCommands for managing experiments in MLFlow.
modelsCommands for managing models in MLFlow.
Usage
d3x mlflow experiments [OPTIONS] COMMAND [ARGS]...d3x mlflow experiments --helpFunction
Commands for managing experiments in MLFlow.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
archiveArchive experiment in MLFlow
deleteDelete experiment in MLFlow
listList experiments in MLFlow
restoreRestore experiment in MLFlow
Usage
d3x mlflow experiments archive [OPTIONS] IDd3x mlflow experiments archive --helpFunction
Archive experiment in MLFlow.
Options
Option
Description
--helpShow help for the command..
Usage
d3x mlflow experiments delete [OPTIONS] IDd3x mlflow experiments delete --helpFunction
Delete experiment in MLFlow.
Options
Option
Description
--helpShow help for the command..
Usage
d3x mlflow experiments list [OPTIONS]d3x mlflow experiments list --helpFunction
List experiments in MLFlow.
Options
Option
Description
--helpShow help for the command..
Usage
d3x mlflow experiments restore [OPTIONS] IDd3x mlflow experiments restore --helpFunction
Restore experiment in MLFlow.
Options
Option
Description
--helpShow help for the command..
Usage
d3x mlflow models [OPTIONS] COMMAND [ARGS]...d3x mlflow models --helpFunction
Commands for managing models in MLFlow.
Options
Option
Description
--helpShow help for the command.
Commands
Command
Description
deleteDelete model in MLFlow
importImport saved model to MLFlow
listList models registered in MLFlow registry
Usage
d3x mlflow models delete [OPTIONS] NAMEd3x mlflow models delete --helpFunction
Delete model in MLFlow.
Options
Option
Description
--helpShow help for the command..
Usage
d3x mlflow models import [OPTIONS]d3x mlflow models import --helpFunction
Import saved model to MLFlow.
Options
Option
Description
--class_path TEXTPytorch class file path
--class_instance TEXTClass instance
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x mlflow models list [OPTIONS]d3x mlflow models list --helpFunction
List models registered in MLFlow registry.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
d3x mount¶
Usage
d3x mount [OPTIONS] [BUCKET] [MOUNTPATH]d3x mount --helpFunction
Mount S3 bucket in read/write mode.
Options
Option
Description
-a,--allMounts all the previous buckets.
--helpShow help for the command.
d3x profile¶
Usage
d3x profile [OPTIONS] COMMAND [ARGS]...d3x profile --helpFunction
Commands regarding user profiles in DKubeX.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
configureConfigure user profile.
deleteDelete user profile.
listList user profiles.
setSet default user profile.
Usage
d3x profile configure [OPTIONS]d3x profile configure --helpFunction
Configure user profile.
Options
Option
Description
--helpShow help for the command..
Usage
d3x profile delete [OPTIONS] PROFILEd3x profile delete --helpFunction
Delete user profile.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x profile list [OPTIONS]d3x profile list --helpFunction
List user profiles.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x profile set [OPTIONS] PROFILEd3x profile set --helpFunction
Set default user profile.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
d3x qagen¶
Usage
d3x qagen [OPTIONS] COMMAND [ARGS]...d3x qagen --helpFunction
Commands for question and answer generation.
Options
Option
Description
--helpShow help for the command.
Commands
Command
Description
deleteDelete qagen job
generateGenerate questions and answers
jobsList qagen jobs currently active
logsQagen job logs
Usage
d3x qagen delete [OPTIONS] NAMEd3x qagen delete --helpFunction
Delete qagen job.
Options
Option
Description
--helpShow help for the command.
Usage
d3x qagen generate [OPTIONS]d3x qagen generate --helpFunction
Generate questions and answers.
Options
Option
Description
-i,--inpath TEXTInput file or directory path [required]
-p,--promptfile TEXTPromptfile file path [required]
-o,--outpath TEXTOutput directory path [required]
-k,--api_key TEXTAPI key for the model or OPENAI API KEY [required]
-b,--model_base_url TEXTModel base URL for the model, do not pass it in case of OPENAI
--helpShow help for the command.
Usage
d3x qagen jobs [OPTIONS]d3x qagen jobs --helpFunction
List qagen jobs currently active.
Options
Option
Description
--helpShow help for the command.
Usage
d3x qagen logs [OPTIONS] NAMEd3x qagen logs --helpFunction
Qagen job logs.
Options
Option
Description
--helpShow help for the command.
d3x ray¶
Usage
d3x ray [OPTIONS] COMMAND [ARGS]...d3x ray --helpFunction
Commands regarding Ray jobs and Ray clusters.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
activateSet Ray cluster as active cluster.
addressList Ray clusters along with their cluster Ray address.
createCreate Ray cluster.
dashboardOpen Ray dashboard.
deleteDelete Ray cluster.
getGet a Ray cluster.
jobCommands regarding managing Ray jobs in currently active Ray cluster.
listList Ray clusters.
Usage
d3x ray activate [OPTIONS] CLUSTERd3x ray activate --helpFunction
Set Ray cluster as active cluster.
Options
Option
Description
-u,--user TEXTName of the ray cluster owner
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x ray address [OPTIONS]d3x ray address --helpFunction
List Ray clusters along with their cluster Ray address.
Options
Option
Description
-a,--allList all compute templates from all users
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x ray create [OPTIONS]d3x ray create --helpFunction
Create Ray cluster.
Options
Option
Description
-n,--name TEXTname of the ray cluster [required]
-v,--version TEXTversion of the ray cluster (default 2.8.0)
-i,--image TEXTimage of ray head/worker node
--cpu INTEGERray worker node CPU (default 2)
--gpu INTEGERray worker node GPU (default 0)
--memory INTEGERray worker node memory in GB (default 4)
--hcpu INTEGERray head node CPU (default 2)
--hgpu INTEGERray head node GPU (default 0)
--hmemory INTEGERray head node memory in GB (default 4)
--htype TEXTray worker head node instance type
--type TEXTray worker node instance type
--dockerserver TEXTdocker registry url
--dockeruser TEXTdocker registry username
--dockerpsw TEXTdocker registry password
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x ray dashboard [OPTIONS]d3x ray dashboard --helpFunction
Open Ray dashboard.
Options
Option
Description
--helpShow help for the command..
Usage
d3x ray delete [OPTIONS] NAMEd3x ray delete --helpFunction
Delete Ray cluster.
Options
Option
Description
-u,--user TEXTName of the ray cluster owner
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x ray get [OPTIONS]d3x ray get --helpFunction
Get a Ray Cluster.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x ray job [OPTIONS] COMMAND [ARGS]...d3x ray job --helpFunction
Commands regarding managing Ray jobs in currently active Ray cluster.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
deleteDeletes a stopped job and its associated data from memory.
listLists all running jobs and their information.
logsGets the logs of a job.
showQueries for show details of job.
statusQueries for the current status of a job.
stopAttempts to stop a job.
submitSubmits a job to be run on the cluster.
Usage
d3x ray job delete [OPTIONS] JOB_IDd3x ray job delete --helpFunction
Deletes a stopped job and its associated data from memory.
Note
Only supported for jobs that are already in a terminal state. Fails with exit code 1 if the job is not already stopped. Does not delete job logs from disk. Submitting a job with the same submission ID as a previously deleted job is not supported and may lead to unexpected behavior.
PublicAPI (alpha): This API is in alpha and may change before becoming stable.
Options
Option
Description
--address TEXTAddress of the Ray cluster to connect to. Can also be specified using the RAY_ADDRESS environment variable.
--verify BOOL | TEXTBoolean indication to verify the server’s TLS certificate or a path to a file or directory of trusted certificates. [default: True]
--headers TEXTUsed to pass headers through http/s to the Ray Cluster. Please follow JSON formatting.
--log-style [auto|record|pretty]If ‘pretty’, outputs with formatting and color. If ‘record’, outputs record-style ‘pretty’, and disables pretty logging if stdin is not a TTY.
--log-color [auto|false|true]Use color logging. Auto enables color logging if stdout is a TTY.
-v,--verboseActivates verbose logging.
--helpShow help for the command..
Usage
d3x ray job list [OPTIONS]d3x ray job list --helpFunction
Lists all running jobs and their information.
Options
Option
Description
--address TEXTAddress of the Ray cluster to connect to. Can also be specified using the RAY_ADDRESS environment variable.
--verify BOOL | TEXTBoolean indication to verify the server’s TLS certificate or a path to a file or directory of trusted certificates. [default: True]
--headers TEXTUsed to pass headers through http/s to the Ray Cluster. Please follow JSON formatting.
--log-style [auto|record|pretty]If ‘pretty’, outputs with formatting and color. If ‘record’, outputs record-style ‘pretty’, and disables pretty logging if stdin is not a TTY.
--log-color [auto|false|true]Use color logging. Auto enables color logging if stdout is a TTY.
-v,--verboseActivates verbose logging.
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x ray job logs [OPTIONS] JOB_IDd3x ray job logs --helpFunction
Gets the logs of a job.
Options
Option
Description
--address TEXTAddress of the Ray cluster to connect to. Can also be specified using the RAY_ADDRESS environment variable.
-f,--followIf set, follow the logs (like tail -f).
--verify BOOL | TEXTBoolean indication to verify the server’s TLS certificate or a path to a file or directory of trusted certificates. [default: True]
--headers TEXTUsed to pass headers through http/s to the Ray Cluster. Please follow JSON formatting.
--log-style [auto|record|pretty]If ‘pretty’, outputs with formatting and color. If ‘record’, outputs record-style ‘pretty’, and disables pretty logging if stdin is not a TTY.
--log-color [auto|false|true]Use color logging. Auto enables color logging if stdout is a TTY.
-v,--verboseActivates verbose logging.
--helpShow help for the command..
Usage
d3x ray job show [OPTIONS] JOB_IDd3x ray job show --helpFunction
Queries for show details of job.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x ray job status [OPTIONS] JOB_IDd3x ray job status --helpFunction
Queries for the current status of a job.
Options
Option
Description
--address TEXTAddress of the Ray cluster to connect to. Can also be specified using the RAY_ADDRESS environment variable.
--verify BOOL | TEXTBoolean indication to verify the server’s TLS certificate or a path to a file or directory of trusted certificates. [default: True]
--headers TEXTUsed to pass headers through http/s to the Ray Cluster. Please follow JSON formatting.
--log-style [auto|record|pretty]If ‘pretty’, outputs with formatting and color. If ‘record’, outputs record-style ‘pretty’, and disables pretty logging if stdin is not a TTY.
--log-color [auto|false|true]Use color logging. Auto enables color logging if stdout is a TTY.
-v,--verboseActivates verbose logging.
--helpShow help for the command..
Usage
d3x ray job stop [OPTIONS] JOB_IDd3x ray job stop --helpFunction
Attempts to stop a job.
Options
Option
Description
--address TEXTAddress of the Ray cluster to connect to. Can also be specified using the RAY_ADDRESS environment variable.
--no-waitIf set, will not wait for the job to exit.
--verify BOOL | TEXTBoolean indication to verify the server’s TLS certificate or a path to a file or directory of trusted certificates. [default: True]
--headers TEXTUsed to pass headers through http/s to the Ray Cluster. Please follow JSON formatting.
--log-style [auto|record|pretty]If ‘pretty’, outputs with formatting and color. If ‘record’, outputs record-style ‘pretty’, and disables pretty logging if stdin is not a TTY.
--log-color [auto|false|true]Use color logging. Auto enables color logging if stdout is a TTY.
-v,--verboseActivates verbose logging.
--helpShow help for the command..
Usage
d3x ray job submit [OPTIONS] ENTRYPOINT...d3x ray job submit --helpFunction
Submits a job to be run on the cluster.
Options
Option
Description
--address TEXTAddress of the Ray cluster to connect to. Can also be specified using the RAY_ADDRESS environment variable.
--job-id TEXTDEPRECATED: Use –submission-id instead.
--submission-id TEXTSubmission ID to specify for the job. If not provided, one will be generated.
--runtime-env TEXTPath to a local YAML file containing a runtime_env definition.
--runtime-env-json TEXTJSON-serialized runtime_env dictionary.
--working-dir TEXTDirectory containing files that your job will run in. Can be a local directory or a remote URI to a .zip file (S3, GS, HTTP). If specified, this overrides the option in –runtime-env.
--metadata-json TEXTJSON-serialized dictionary of metadata to attach to the job.
--entrypoint-num-cpus FLOATthe quantity of CPU cores to reserve for the entrypoint command, separately from any tasks or actors that are launched by it
--entrypoint-num-gpus FLOATthe quantity of GPUs to reserve for the entrypoint command, separately from any tasks or actors that are launched by it
--entrypoint-resources TEXTa JSON-serialized dictionary mapping resource name to resource quantity describing resources to reserve for the entrypoint command, separately from any tasks or actors that are launched by it
--no-waitIf set, will not stream logs and wait for the job to exit.
--verify BOOL | TEXTBoolean indication to verify the server’s TLS certificate or a path to a file or directory of trusted certificates. [default: True]
--headers TEXTUsed to pass headers through http/s to the Ray Cluster. Please follow JSON formatting
--log-style [auto|record|pretty]If ‘pretty’, outputs with formatting and color. If ‘record’, outputs record-style without formatting. ‘auto’ defaults to ‘pretty’, and disables pretty logging if stdin is not a TTY.
--log-color [auto|false|true]Use color logging. Auto enables color logging if stdout is a TTY.
-v,--verboseActivates verbose logging.
--helpShow help for the command..
Usage
d3x ray list [OPTIONS]d3x ray list --helpFunction
List Ray Clusters
Options
Option
Description
--allList all Ray clusters from all users
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
d3x restore¶
Usage
d3x restore [OPTIONS] COMMAND [ARGS]...d3x restore --helpFunction
Commands for restoring databases.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
weaviateCommand for Weaviate restore.
Usage
d3x restore weaviate [OPTIONS]d3x restore weaviate --helpFunction
Command for Weaviate restore.
Options
Option
Description
-i,--id TEXTAn ID for the backup [required]
-b,--backend [filesystem|s3]S3 or filesystem to save the backup [required]
--helpShow help for the command..
d3x serve¶
Usage
d3x serve [OPTIONS] COMMAND [ARGS]...d3x serve --helpFunction
Commands for creating model deployments.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
createCreate deployment
deleteDelete deployment
getGet Deployment
listList Deployments
statusCheck deployment Status
Usage
d3x serve create [OPTIONS]d3x serve create --helpFunction
Create deployment.
Options
Option
Description
-n,--name TEXTname of the ray serve [required]
-r,--registry_type [hugging_face|mlflow|local|none]registry type [required]
--hface_repoid TEXThugging face repo id
--hface_tokenizer TEXThugging face tokenizer
--hface_classifier TEXThugging face classifier
--hface_token TEXThugging face token
--model TEXTmlflow model name
--model_version TEXTmlflow model version
--depfilepath TEXTdeployment filepath
--working_dir TEXTlocal serving directory path
--is_private_repoprivate repo
--repo_name TEXTgithub repo name
--repo_org TEXTgithub personal/organization account
--access_token TEXTgithub access token
--branch_name TEXTgithub branch name
--commit_id TEXTgithub commit id
--unprotectedserving without token
-e,--env TEXTenvironment variable
--ngpus TEXTnumber of gpus
--min_cpu TEXTmin number of cpus for cluster creation
--max_cpu TEXTmax number of cpus per cluster creation
--min_memory TEXTmin memory for cluster cluster creation
--max_memory TEXTmax memory for cluster cluster creation
--min_replicas TEXTmin deployment replicas
--max_replicas TEXTmax deployment replicas
--max_concurrent_requests TEXTmax concurrent requests
--description TEXTdeployment description
--image TEXTcluster image
--publishpublish the deployment
--no_rsrc_limitsno resource limits
--type TEXTnode selector
--timeout INTEGERdeployment timeout
--kserveenable kserve deployment
--model_format [tensorflow|sklearn|pytorch|xgboost|pmml|lightgbm|paddle|mlflow|custom]model format in case of kserve deployment
--model_path TEXTlocal path of model for kserve deployment
--protocol_version [v1|v2]dataplane protocol
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x serve delete [OPTIONS] NAMEd3x serve delete --helpFunction
Delete deployment.
Options
Option
Description
-u,--user TEXTDeployment owner name
-p,--publishedPublished deployment
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x serve get [OPTIONS] NAMEd3x serve get --helpFunction
Get deployment.
Options
Option
Description
-u,--user TEXTDeployment owner name
-p,--publishedPublished deployment
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x serve list [OPTIONS]d3x serve list --helpFunction
List deployments.
Options
Option
Description
--allList all the deployments
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x serve status [OPTIONS] NAMESPACE IDd3x serve status --helpFunction
Check deployment Status.
Options
Option
Description
--helpShow help for the command..
d3x sky¶
Usage
d3x sky [OPTIONS] COMMAND [ARGS]...d3x sky --helpFunction
Commands for managing SkyPilot clusters, resources and jobs.
Options
Option
Description
--install-shell-completion [bash|zsh|fish|auto]Install shell completion for the specified shell.
--uninstall-shell-completion [bash|zsh|fish|auto]Uninstall shell completion for the specified shell.
-v,--versionShow the version and exit.
-c,--commitShow the commit hash and exit
-h,--helpShow help for the command..
Commands
Command
Description
launchLaunch a cluster or task.
execExecute a task or command on an existing cluster.
statusShow clusters.
cost-reportShow estimated costs for launched clusters.
queueShow the job queue for cluster(s).
logsTail the log of a job.
cancelCancel job(s).
stopStop cluster(s).
autostopSchedule an autostop or autodown for cluster(s).
startRestart cluster(s).
downTear down cluster(s).
checkCheck which clouds are available to use.
show-gpusShow supported GPU/TPU/accelerators and their prices.
storageCommands for using SkyPilot Storage CLI.
benchCommands for usingSkyPilot Benchmark CLI.
jobsCommands for using SkyPilot managed Jobs CLI.
spotCommands for using managed Spot CLI (spot instances with auto-recovery).
serveCommands for using SkyServe CLI (multi-region, multi-cloud serving).
Usage
d3x sky launch [OPTIONS] [ENTRYPOINT]...d3x sky launch --helpFunction
Launch a cluster or task. If ENTRYPOINT points to a valid YAML file, it is read in as the task specification. Otherwise, it is interpreted as a bash command. In both cases, the commands are run under the task’s workdir (if specified) and they undergo job queue scheduling.
Options
Option
Description
-c,--cluster TEXTA cluster name. If provided, either reuse an existing cluster with that name or provision a new cluster with that name. Otherwise provision a new cluster with an autogenerated name.
--dryrunIf True, do not actually run the job.
-s,--detach-setupIf True, run setup in non-interactive mode as part of the job itself. You can safely ctrl-c to detach from logging, and it will not interrupt the setup process. To see the logs again after detaching, use sky logs. To cancel setup, cancel the job via sky cancel. Useful for long-running setup commands.
-d,--detach-runIf True, as soon as a job is submitted, return from this call and do not stream execution logs.
--dockerIf used, runs locally inside a docker container.
-n,--name TEXTTask name. Overrides the ‘name’ config in the YAML if both are supplied.
--workdir DIRECTORYIf specified, sync this dir to the remote working directory, where the task will be invoked. Overrides the ‘workdir’ config in the YAML if both are supplied.
--cloud TEXTThe cloud to use. If specified, overrides the ‘resources.cloud’ config. Passing ‘none’ resets the config.
--region TEXTThe region to use. If specified, overrides the ‘resources.region’ config. Passing ‘none’ resets the config.
--zone TEXTThe zone to use. If specified, overrides the ‘resources.zone’ config. Passing ‘none’ resets the config.
--num-nodes INTEGERNumber of nodes to execute the task on. Overrides the ‘num_nodes’ config in the YAML if both are supplied.
--cpus TEXTNumber of vCPUs each instance must have (e.g.,
--cpus=4(exactly 4) or--cpus=4+(at least 4)). This is used to automatically select the instance type.--memory TEXTAmount of memory each instance must have (e.g.,
--memory=4(exactly 4 GB) or--memory=4+(at least 4 GB)). This is used to automatically select the instance type.--hcpu INTEGERHead node CPU. Overrides the ‘resources.head_cpu’ config in the YAML if both are supplied.
--hmemory INTEGERHead node memory in GB. Overrides the ‘resources.head_memory’ config in the YAML if both are supplied.
--htype TEXTHead node instance type. Overrides the ‘resources.head_instance_type’ config in the YAML if both are supplied.
--disk-size INTEGEROS disk size in GBs.
--disk-tier [low|medium|high|best|none]OS disk tier. Could be one of low, medium, high, best, none. If best is specified, use the best possible disk tier. If none is specified, enforce to use default value and override the option in task YAML. Default: medium
--use-spot / --no-use-spotWhether to request spot instances. If specified, overrides the ‘resources.use_spot’ config.
--image-id TEXTCustom image id for launching the instances. Passing ‘none’ resets the config.
--env-file DOTENV_VALUESPath to a dotenv file with environment variables to set on the remote node.
--env _PARSE_ENV_VAREnvironment variable to set on the remote node. It can be specified multiple times. Examples: 1.
--env MY_ENV=1: set$MY_ENVon the cluster to be 1. 2.--env MY_ENV2=$HOME: set$MY_ENV2on the cluster to be the same value of$HOMEin the local environment where the CLI command is run. 3.--env MY_ENV3: set$MY_ENV3on the cluster to be the same value of$MY_ENV3in the local environment.--gpus TEXTType and number of GPUs to use. Example values: ‘V100:8’, ‘V100’ (short for a count of 1), or ‘V100:0.5’ (fractional counts are supported by the scheduling framework). If a new cluster is being launched by this command, this is the resources to provision. If an existing cluster is being reused, this is seen as the task demand, which must fit the cluster’s total resources and is used for scheduling the task. Overrides the ‘accelerators’ config in the YAML if both are supplied. Passing ‘none’ resets the config.
-t,--instance-type TEXTThe instance type to use. If specified, overrides the ‘resources.instance_type’ config. Passing ‘none’ resets the config.
--ports TEXTPorts to open on the cluster. If specified, overrides the ‘ports’ config in the YAML.
-i,--idle-minutes-to-autostop INTEGERAutomatically stop the cluster after this many minutes of idleness, i.e., no running or pending jobs in the cluster’s job queue. Idleness gets reset whenever setting-up/running/pending jobs are found in the job queue. Setting this flag is equivalent to running
sky launch -d ...and thensky autostop -i <minutes>. If not set, the cluster will not be autostopped.--downAutodown the cluster: tear down the cluster after all jobs finish (successfully or abnormally). If –idle-minutes-to-autostop is also set, the cluster will be torn down after the specified idle time. Note that if errors occur during provisioning/data syncing/setting up, the cluster will not be torn down for debugging purposes.
-r,--retry-until-upWhether to retry provisioning infinitely until the cluster is up, if we fail to launch the cluster on any possible region/cloud due to unavailability errors.
-y,--yesSkip confirmation prompt.
--no-setupSkip setup phase when (re-)launching cluster.
--clone-disk-from,--clone TEXT[Experimental] Clone disk from an existing cluster to launch a new one. This is useful when the new cluster needs to have the same data on the boot disk as an existing cluster.
-h,--helpShow help for the command..
Usage
d3x sky exec [OPTIONS] CLUSTER ENTRYPOINT...d3x sky exec --helpFunction
Execute a task or command on an existing cluster. If ENTRYPOINT points to a valid YAML file, it is read in as the task specification. Otherwise, it is interpreted as a bash command.
Options
Option
Description
-d,--detach-runIf True, as soon as a job is submitted, return from this call and do not stream execution logs.
-n,--name TEXTTask name. Overrides the ‘name’ config in the YAML if both are supplied.
--workdir DIRECTORYIf specified, sync this dir to the remote working directory, where the task will be invoked. Overrides the ‘workdir’ config in the YAML if both are supplied.
--cloud TEXTThe cloud to use. If specified, overrides the ‘resources.cloud’ config. Passing ‘none’ resets the config.
--region TEXTThe region to use. If specified, overrides the ‘resources.region’ config. Passing ‘none’ resets the config.
--zone TEXTThe zone to use. If specified, overrides the ‘resources.zone’ config. Passing ‘none’ resets the config.
--num-nodes INTEGERNumber of nodes to execute the task on. Overrides the ‘num_nodes’ config in the YAML if both are supplied.
--cpus TEXTNumber of vCPUs each instance must have (e.g.,
--cpus=4(exactly 4) or--cpus=4+(at least 4)). This is used to automatically select the instance type.--memory TEXTAmount of memory each instance must have in GB (e.g.,
--memory=16(exactly 16GB),--memory=16+(at least 16GB))--disk-size INTEGEROS disk size in GBs.
--disk-tier [low|medium|high|best|none]OS disk tier. Could be one of low, medium, high, best, none. If best is specified, use the best possible disk tier. If none is specified, enforce to use default value and override the option in task YAML. Default: medium
--use-spot / --no-use-spotWhether to request spot instances. If specified, overrides the ‘resources.use_spot’ config.
--image-id TEXTCustom image id for launching the instances. Passing ‘none’ resets the config.
--env-file DOTENV_VALUESPath to a dotenv file with environment variables to set on the remote node.
--env _PARSE_ENV_VAREnvironment variable to set on the remote node. It can be specified multiple times. Examples: 1.
--env MY_ENV=1: set$MY_ENVon the cluster to be 1. 2.--env MY_ENV2=$HOME: set$MY_ENV2on the cluster to be the same value of$HOMEin the local environment where the CLI command is run. 3.--env MY_ENV3: set$MY_ENV3on the cluster to be the same value of$MY_ENV3in the local environment.--gpus TEXTType and number of GPUs to use. Example values: ‘V100:8’, ‘V100’ (short for a count of 1), or ‘V100:0.5’ (fractional counts are supported by the scheduling framework). If a new cluster is being launched by this command, this is the resources to provision. If an existing cluster is being reused, this is seen as the task demand, which must fit the cluster’s total resources and is used for scheduling the task. Overrides the ‘accelerators’ config in the YAML if both are supplied. Passing ‘none’ resets the config.
-t,--instance-type TEXTThe instance type to use. If specified, overrides the ‘resources.instance_type’ config. Passing ‘none’ resets the config.
--ports TEXTPorts to open on the cluster. If specified, overrides the ‘ports’ config in the YAML.
-h,--helpShow help for the command..
Usage
d3x sky status [OPTIONS] [CLUSTERS]...d3x sky status --helpFunction
Show sky clusters. If CLUSTERS is given, show those clusters. Otherwise, show all clusters. If –ip is specified, show the IP address of the head node of the cluster. Only available when CLUSTERS contains exactly one cluster, e.g.
sky status --ip mycluster. If –endpoints is specified, show all exposed endpoints in the cluster. Only available when CLUSTERS contains exactly one cluster, e.g.sky status --endpoints mycluster. To query a single endpoint, you can usesky status mycluster --endpoint 8888.Options
Option
Description
-a,--allShow all information in full.
-r,--refreshQuery the latest cluster statuses from the cloud provider(s).
--ipGet the IP address of the head node of a cluster. This option will override all other options. For Kubernetes clusters, the returned IP address is the internal IP of the head pod, and may not be accessible from outside the cluster.
--endpointsGet all exposed endpoints and corresponding URLs for acluster. This option will override all other options.
--endpoint INTEGERGet the endpoint URL for the specified port number on the cluster. This option will override all other options.
--show-spot-jobs / --no-show-spot-jobsAlso show recent in-progress spot jobs, if any.
--show-services / --no-show-servicesAlso show sky serve services, if any.
-h,--helpShow help for the command..
Usage
d3x sky cost-report [OPTIONS]d3x sky cost-report --helpFunction
Show estimated costs for launched Skypilot clusters.
Options
Option
Description
-a,--allShow all information in full.
-h,--helpShow help for the command..
Usage
d3x sky queue [OPTIONS] [CLUSTERS]...d3x sky queue --helpFunction
Show the job queue for cluster(s).
Options
Option
Description
-a,--all-usersShow all users’ information in full.
-s,--skip-finishedShow only pending/running jobs’ information.
-h,--helpShow help for the command..
Usage
d3x sky logs [OPTIONS] CLUSTER [JOB_IDS]...d3x sky logs --helpFunction
Tail the log of a job.
Options
Option
Description
-s,--sync-downSync down the logs of a job to the local machine. For a distributed job, a separate log file from each worker will be downloaded.
--statusIf specified, do not show logs but exit with a status code for the job’s status: 0 for succeeded, or 1 for all other statuses.
--follow / --no-followFollow the logs of a job. If –no-follow is specified, print the log so far and exit. [default: –follow]
-h,--helpShow help for the command..
Usage
d3x sky cancel [OPTIONS] CLUSTER [JOBS]...d3x sky cancel --helpFunction
Cancel Skypilot job(s).
Options
Option
Description
-a,--allCancel all jobs on the specified cluster.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky stop [OPTIONS] [CLUSTERS]...d3x sky stop --helpFunction
Stop Skypilot cluster(s).
Options
Option
Description
-a,--allStop all existing clusters.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky autostop [OPTIONS] [CLUSTERS]...d3x sky autostop --helpFunction
Schedule an autostop or autodown for cluster(s). Autostop/autodown will automatically stop or teardown a cluster when it becomes idle for a specified duration. Idleness means there are no in-progress (pending/running) jobs in a cluster’s job queue.
Options
Option
Description
-a,--allApply this command to all existing clusters.
-i,--idle-minutes INTEGERSet the idle minutes before autostopping the cluster. See the doc above for detailed semantics.
--cancelCancel any currently active auto{stop,down} setting for the cluster. No-op if there is no active setting.
--downUse autodown (tear down the cluster; non-restartable), instead of autostop (restartable).
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky start [OPTIONS] [CLUSTERS]...d3x sky start --helpFunction
Restart Skypilot cluster(s). If a cluster is previously stopped (status is STOPPED) or failed in provisioning/runtime installation (status is INIT), this command will attempt to start the cluster. In the latter case, provisioning and runtime installation will be retried.
Options
Option
Description
-a,--allStart all existing clusters.
-y,--yesSkip confirmation prompt.
-i,--idle-minutes-to-autostop INTEGERAutomatically stop the cluster after this many minutes of idleness, i.e., no running or pending jobs in the cluster’s job queue. Idleness gets reset whenever setting-up/running/pending jobs are found in the job queue. Setting this flag is equivalent to running
sky launch -d ...and thensky autostop -i <minutes>. If not set, the cluster will not be autostopped.--downAutodown the cluster: tear down the cluster after specified minutes of idle time after all jobs finish (successfully or abnormally). Requires –idle-minutes-to-autostop to be set.
-r,--retry-until-upRetry provisioning infinitely until the cluster is up, if we fail to start the cluster due to unavailability errors.
-f,--forceForce start the cluster even if it is already UP. Useful for upgrading the SkyPilot runtime on the cluster.
-h,--helpShow help for the command..
Usage
d3x sky down [OPTIONS] [CLUSTERS]...d3x sky down --helpFunction
Tear down Skypilot cluster(s).
Options
Option
Description
-a,--allTear down all existing clusters.
-y,--yesSkip confirmation prompt.
-p,--purgeIgnore cloud provider errors (if any). Useful for cleaning up manually deleted cluster(s).
-h,--helpShow help for the command..
Usage
d3x sky check [OPTIONS]d3x sky check --helpFunction
Check which clouds are available to use by Skypilot.
Options
Option
Description
-v,--verboseShow the activated account for each cloud.
-h,--helpShow help for the command..
Usage
d3x sky show-gpus [OPTIONS] [ACCELERATOR_STR]d3x sky show-gpus --helpFunction
Show GPU/TPU/accelerators supported by Skypilot and their prices.
Options
Option
Description
-a,--allShow details of all GPU/TPU/accelerator offerings.
--cloud TEXTCloud provider to query.
--region TEXTThe region to use. If not specified, shows accelerators from all regions.
--all-regionsShow pricing and instance details for a specified accelerator across all regions and clouds.
-h,--helpShow help for the command..
Usage
d3x sky storage [OPTIONS] COMMAND [ARGS]...d3x sky storage --helpFunction
Commands for using SkyPilot storage CLI.
Options
Option
Description
-h,--helpShow help for the command..
Commands
Command
Description
lsList storage objects managed by SkyPilot.
deleteDelete storage objects.
Usage
d3x sky storage ls [OPTIONS]d3x sky storage ls --helpFunction
List storage objects managed by SkyPilot.
Options
Option
Description
-a,--allShow all information in full.
-h,--helpShow help for the command..
Usage
d3x sky storage delete [OPTIONS] [NAMES]...d3x sky storage delete --helpFunction
Delete storage objects in Skypilot storage.
Options
Option
Description
-a,--allDelete all storage objects.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky bench [OPTIONS] COMMAND [ARGS]...d3x sky bench --helpFunction
Commands for using SkyPilot Benchmark CLI.
Options
Option
Description
-h,--helpShow help for the command..
Commands
Command
Description
launchBenchmark a task on different resources.
lsList the benchmark history.
showShow a benchmark report.
downTear down all clusters belonging to a benchmark.
deleteDelete benchmark reports from the history.
Usage
d3x sky bench launch [OPTIONS] ENTRYPOINT...d3x sky bench launch --helpFunction
Benchmark a task on different resources.
Options
Option
Description
-b,--benchmark TEXTBenchmark name. [required]
-n,--name TEXTTask name. Overrides the ‘name’ config in the YAML if both are supplied.
--workdir DIRECTORYIf specified, sync this dir to the remote working directory, where the task will be invoked. Overrides the ‘workdir’ config in the YAML if both are supplied.
--cloud TEXTThe cloud to use. If specified, overrides the ‘resources.cloud’ config. Passing ‘none’ resets the config.
--region TEXTThe region to use. If specified, overrides the ‘resources.region’ config. Passing ‘none’ resets the config.
--zone TEXTThe zone to use. If specified, overrides the ‘resources.zone’ config. Passing ‘none’ resets the config.
--num-nodes INTEGERNumber of nodes to execute the task on. Overrides the ‘num_nodes’ config in the YAML if both are supplied.
--cpus TEXTNumber of vCPUs each instance must have (e.g.,
--cpus=4(exactly 4) or--cpus=4+(at least 4)). This is used to automatically select the instance type.--memory TEXTAmount of memory each instance must have in GB (e.g.,
--memory=16(exactly 16GB),--memory=16+(at least 16GB))--disk-size INTEGEROS disk size in GBs.
--disk-tier [low|medium|high|best|none]OS disk tier. Could be one of low, medium, high, best, none. If best is specified, use the best possible disk tier. If none is specified, enforce to use default value and override the option in task YAML. Default: medium
--use-spot / --no-use-spotWhether to request spot instances. If specified, overrides the ‘resources.use_spot’ config.
--image-id TEXTCustom image id for launching the instances. Passing ‘none’ resets the config.
--env-file DOTENV_VALUESPath to a dotenv file with environment variables to set on the remote node.
--env _PARSE_ENV_VAREnvironment variable to set on the remote node. It can be specified multiple times. Examples: 1.
--env MY_ENV=1: set$MY_ENVon the cluster to be 1. 2.--env MY_ENV2=$HOME: set$MY_ENV2on the cluster to be the same value of$HOMEin the local environment where the CLI command is run. 3.--env MY_ENV3: set$MY_ENV3on the cluster to be the same value of$MY_ENV3in the local environment.--gpus TEXTComma-separated list of GPUs to run benchmark on. Example values: ‘T4:4,V100:8’ (without blank spaces).
--ports TEXTPorts to open on the cluster. If specified, overrides the ‘ports’ config in the YAML.
-i,--idle-minutes-to-autostop INTEGERAutomatically stop the cluster after this many minutes of idleness after setup/file_mounts. This is equivalent to running sky launch -d … and then sky autostop -i <minutes>. If not set, the cluster will not be autostopped.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky bench ls [OPTIONS]d3x sky bench ls --helpFunction
List the benchmark history.
Options
Option
Description
-h,--helpShow help for the command..
Usage
d3x sky bench show [OPTIONS] BENCHMARKd3x sky bench show --helpFunction
Show a benchmark report.
Options
Option
Description
-h,--helpShow help for the command..
Usage
d3x sky bench down [OPTIONS] BENCHMARKd3x sky bench down --helpFunction
Tear down all clusters belonging to a benchmark.
Options
Option
Description
-e,--exclude TEXTCluster name(s) to exclude from termination. Typically, you might want to see the benchmark results in sky bench show and exclude a ‘winner’ cluster from termination to finish the running task.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky bench delete [OPTIONS] [BENCHMARKS]...d3x sky bench delete --helpFunction
Delete benchmark reports from the history.
Options
Option
Description
-a,--allDelete all benchmark reports from the history.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command.
Usage
d3x sky jobs [OPTIONS] COMMAND [ARGS]...d3x sky jobs --helpFunction
Commands for using SkyPilot managed jobs CLI.
Options
Option
Description
-h,--helpShow help for the command..
Commands
Command
Description
launchLaunch a managed job from a YAML or a command.
queueShow statuses of managed jobs.
cancelCancel managed jobs.
logsTail the log of a managed job.
dashboardOpens a dashboard for managed jobs (needs controller to be UP).
Usage
d3x sky jobs launch [OPTIONS] ENTRYPOINT...d3x sky jobs launch --helpFunction
Launch a managed job from a YAML or a command.
Options
Option
Description
-n,--name TEXTTask name. Overrides the ‘name’ config in the YAML if both are supplied.
--workdir DIRECTORYIf specified, sync this dir to the remote working directory, where the task will be invoked. Overrides the ‘workdir’ config in the YAML if both are supplied.
--cloud TEXTThe cloud to use. If specified, overrides the ‘resources.cloud’ config. Passing ‘none’ resets the config.
--region TEXTThe region to use. If specified, overrides the ‘resources.region’ config. Passing ‘none’ resets the config.
--zone TEXTThe zone to use. If specified, overrides the ‘resources.zone’ config. Passing ‘none’ resets the config.
--num-nodes INTEGERNumber of nodes to execute the task on. Overrides the ‘num_nodes’ config in the YAML if both are supplied.
--cpus TEXTNumber of vCPUs each instance must have (e.g.,
--cpus=4(exactly 4) or--cpus=4+(at least 4)). This is used to automatically select the instance type.--memory TEXTAmount of memory each instance must have in GB (e.g.,
--memory=16(exactly 16GB),--memory=16+(at least 16GB))--disk-size INTEGEROS disk size in GBs.
--disk-tier [low|medium|high|best|none]OS disk tier. Could be one of low, medium, high, best, none. If best is specified, use the best possible disk tier. If none is specified, enforce to use default value and override the option in task YAML. Default: medium
--use-spot / --no-use-spotWhether to request spot instances. If specified, overrides the ‘resources.use_spot’ config.
--image-id TEXTCustom image id for launching the instances. Passing ‘none’ resets the config.
--env-file DOTENV_VALUESPath to a dotenv file with environment variables to set on the remote node.
--env _PARSE_ENV_VAREnvironment variable to set on the remote node. It can be specified multiple times. Examples: 1.
--env MY_ENV=1: set$MY_ENVon the cluster to be 1. 2.--env MY_ENV2=$HOME: set$MY_ENV2on the cluster to be the same value of$HOMEin the local environment where the CLI command is run. 3.--env MY_ENV3: set$MY_ENV3on the cluster to be the same value of$MY_ENV3in the local environment.--gpus TEXTType and number of GPUs to use. Example values: ‘V100:8’, ‘V100’ (short for a count of 1), or ‘V100:0.5’ (fractional counts are supported by the scheduling framework). If a new cluster is being launched by this command, this is the resources to provision. If an existing cluster is being reused, this is seen as the task demand, which must fit the cluster’s total resources and is used for scheduling the task. Overrides the ‘accelerators’ config in the YAML if both are supplied. Passing ‘none’ resets the config.
-t,--instance-type TEXTThe instance type to use. If specified, overrides the ‘resources.instance_type’ config.
--ports TEXTPorts to open on the cluster. If specified, overrides the ‘ports’ config in the YAML.
-d,--detach-runIf True, as soon as a job is submitted, return from this call and do not stream execution logs.
-r,--retry-until-up / --no-retry-until-up(Default: True; this flag is deprecated and will be removed in a future release.) Whether to retry provisioning infinitely until the cluster is up, if unavailability errors are encountered. This applies to launching all managed jobs (both the initial and any recovery attempts), not the jobs controller.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command.
Usage
d3x sky jobs queue [OPTIONS]d3x sky jobs queue --helpFunction
Show statuses of managed jobs.
Options
Option
Description
-a,--allShow all information in full.
-r,--refreshQuery the latest statuses, restarting the jobs controller if stopped.
-s,--skip-finishedShow only pending/running jobs’ information.
-h,--helpShow help for the command..
Usage
d3x sky jobs cancel [OPTIONS] [JOB_IDS]...d3x sky jobs cancel --helpFunction
Cancel managed jobs.
Options
Option
Description
-n,--name TEXTManaged job name to cancel.
-a,--allCancel all managed jobs.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command.
Usage
d3x sky jobs logs [OPTIONS] [JOB_ID]d3x sky jobs logs --helpFunction
Tail the log of a managed job.
Options
Option
Description
-n,--name TEXTManaged job name.
--follow / --no-followFollow the logs of the job. [default: –follow] If –no-follow is specified, print the log so far and exit.
--controllerShow the controller logs of this job; useful for debugging launching/recoveries, etc.
-h,--helpShow help for the command.
Usage
d3x sky jobs dashboard [OPTIONS]d3x sky jobs dashboard --helpFunction
Opens a dashboard for managed jobs (needs controller to be UP).
Options
Option
Description
-p,--port INTEGERLocal port to use for the dashboard. If None, a free port is automatically chosen.
-h,--helpShow help for the command.
Usage
d3x sky spot [OPTIONS] COMMAND [ARGS]...d3x sky spot --helpFunction
Commands for using managed Spot CLI (spot instances with auto-recovery).
Options
Option
Description
-h,--helpShow help for the command..
Commands
Command
Description
launchLaunch a managed spot job from a YAML or a command.
queueShow statuses of managed spot jobs.
cancelCancel managed spot jobs.
logsTail the log of a managed spot job.
dashboardOpens a dashboard for spot jobs (needs controller to be UP).
Usage
d3x sky spot launch [OPTIONS] ENTRYPOINT...d3x sky spot launch --helpFunction
Launch a managed spot job from a YAML or a command.
Options
Option
Description
-n,--name TEXTTask name. Overrides the ‘name’ config in the YAML if both are supplied.
--workdir DIRECTORYIf specified, sync this dir to the remote working directory, where the task will be invoked. Overrides the ‘workdir’ config in the YAML if both are supplied.
--cloud TEXTThe cloud to use. If specified, overrides the ‘resources.cloud’ config. Passing ‘none’ resets the config.
--region TEXTThe region to use. If specified, overrides the ‘resources.region’ config. Passing ‘none’ resets the config.
--zone TEXTThe zone to use. If specified, overrides the ‘resources.zone’ config. Passing ‘none’ resets the config.
--num-nodes INTEGERNumber of nodes to execute the task on. Overrides the ‘num_nodes’ config in the YAML if both are supplied.
--cpus TEXTNumber of vCPUs each instance must have (e.g.,
--cpus=4(exactly 4) or--cpus=4+(at least 4)). This is used to automatically select the instance type.--memory TEXTAmount of memory each instance must have in GB (e.g.,
--memory=16(exactly 16GB),--memory=16+(at least 16GB))--disk-size INTEGEROS disk size in GBs.
--disk-tier [low|medium|high|best|none]OS disk tier. Could be one of low, medium, high, best, none. If best is specified, use the best possible disk tier. If none is specified, enforce to use default value and override the option in task YAML. Default: medium
--use-spot / --no-use-spotWhether to request spot instances. If specified, overrides the ‘resources.use_spot’ config.
--image-id TEXTCustom image id for launching the instances. Passing ‘none’ resets the config.
--env-file DOTENV_VALUESPath to a dotenv file with environment variables to set on the remote node.
--env _PARSE_ENV_VAREnvironment variable to set on the remote node. It can be specified multiple times. Examples: 1.
--env MY_ENV=1: set$MY_ENVon the cluster to be 1. 2.--env MY_ENV2=$HOME: set$MY_ENV2on the cluster to be the same value of$HOMEin the local environment where the CLI command is run. 3.--env MY_ENV3: set$MY_ENV3on the cluster to be the same value of$MY_ENV3in the local environment.--gpus TEXTType and number of GPUs to use. Example values: ‘V100:8’, ‘V100’ (short for a count of 1), or ‘V100:0.5’ (fractional counts are supported by the scheduling framework). If a new cluster is being launched by this command, this is the resources to provision. If an existing cluster is being reused, this is seen as the task demand, which must fit the cluster’s total resources and is used for scheduling the task. Overrides the ‘accelerators’ config in the YAML if both are supplied. Passing ‘none’ resets the config.
-t,--instance-type TEXTThe instance type to use. If specified, overrides the ‘resources.instance_type’ config. Passing ‘none’ resets the config.
--ports TEXTPorts to open on the cluster. If specified, overrides the ‘ports’ config in the YAML.
--spot-recovery TEXTSpot recovery strategy to use for the managed spot task.
-d,--detach-runIf True, as soon as a job is submitted, return from this call and do not stream execution logs.
-r,--retry-until-up / -no-retry-until-up(Default: True; this flag is deprecated and will be removed in a future release.) Whether to retry provisioning infinitely until the cluster is up, if unavailability errors are encountered. This applies to launching the spot clusters (both the initial and any recovery attempts), not the spot controller.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky spot queue [OPTIONS]d3x sky spot queue --helpFunction
Show statuses of managed spot jobs.
Options
Option
Description
-a,--allShow all information in full.
-r,--refreshQuery the latest statuses, restarting the spot controller if stopped.
-s,--skip-finishedShow only pending/running jobs’ information.
-h,--helpShow help for the command..
Usage
d3x sky spot cancel [OPTIONS] [JOB_IDS]...d3x sky spot cancel --helpFunction
Cancel managed spot jobs.
Options
Option
Description
-n,--name TEXTManaged spot job name to cancel.
-a,--allCancel all managed spot jobs.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky spot logs [OPTIONS] [JOB_ID]d3x sky spot logs --helpFunction
Tail the log of a managed spot job.
Options
Option
Description
-n,--name TEXTManaged spot job name.
--follow / --no-followFollow the logs of the job. [default: –follow] If –no-follow is specified, print the log so far and exit.
--controllerShow the controller logs of this job; useful for debugging launching/recoveries, etc.
-h,--helpShow help for the command..
Usage
d3x sky spot dashboard [OPTIONS]d3x sky spot dashboard --helpFunction
Opens a dashboard for spot jobs (needs controller to be UP).
Options
Option
Description
-p,--port INTEGERLocal port to use for the dashboard. If None, a free port is automatically chosen.
-h,--helpShow help for the command..
Usage
d3x sky serve [OPTIONS] COMMAND [ARGS]...d3x sky serve --helpFunction
Commands for using SkyServe CLI (multi-region, multi-cloud serving).
Options
Option
Description
-h,--helpShow help for the command..
Commands
Command
Description
upLaunch a SkyServe service.
updateUpdate a SkyServe service.
statusShow statuses of SkyServe services.
downTeardown service(s).
logsTail the log of a service.
Usage
d3x sky serve up [OPTIONS] SERVICE_YAML...d3x sky serve up --helpFunction
Launch a SkyServe service.
Options
Option
Description
-n,--service-name TEXTA service name. Unique for each service. If not provided, a unique name is autogenerated.
--workdir DIRECTORYIf specified, sync this dir to the remote working directory, where the task will be invoked. Overrides the ‘workdir’ config in the YAML if both are supplied.
--cloud TEXTThe cloud to use. If specified, overrides the ‘resources.cloud’ config. Passing ‘none’ resets the config.
--region TEXTThe region to use. If specified, overrides the ‘resources.region’ config. Passing ‘none’ resets the config.
--zone TEXTThe zone to use. If specified, overrides the ‘resources.zone’ config. Passing ‘none’ resets the config.
--num-nodes INTEGERNumber of nodes to execute the task on. Overrides the ‘num_nodes’ config in the YAML if both are supplied.
--cpus TEXTNumber of vCPUs each instance must have (e.g.,
--cpus=4(exactly 4) or--cpus=4+(at least 4)). This is used to automatically select the instance type.--memory TEXTAmount of memory each instance must have in GB (e.g.,
--memory=16(exactly 16GB),--memory=16+(at least 16GB))--disk-size INTEGEROS disk size in GBs.
--disk-tier [low|medium|high|best|none]OS disk tier. Could be one of low, medium, high, best, none. If best is specified, use the best possible disk tier. If none is specified, enforce to use default value and override the option in task YAML. Default: medium
--use-spot / --no-use-spotWhether to request spot instances. If specified, overrides the ‘resources.use_spot’ config.
--image-id TEXTCustom image id for launching the instances. Passing ‘none’ resets the config.
--env-file DOTENV_VALUESPath to a dotenv file with environment variables to set on the remote node.
--env _PARSE_ENV_VAREnvironment variable to set on the remote node. It can be specified multiple times. Examples: 1.
--env MY_ENV=1: set$MY_ENVon the cluster to be 1. 2.--env MY_ENV2=$HOME: set$MY_ENV2on the cluster to be the same value of$HOMEin the local environment where the CLI command is run. 3.--env MY_ENV3: set$MY_ENV3on the cluster to be the same value of$MY_ENV3in the local environment.--gpus TEXTType and number of GPUs to use. Example values: ‘V100:8’, ‘V100’ (short for a count of 1), or ‘V100:0.5’ (fractional counts are supported by the scheduling framework). If a new cluster is being launched by this command, this is the resources to provision. If an existing cluster is being reused, this is seen as the task demand, which must fit the cluster’s total resources and is used for scheduling the task. Overrides the ‘accelerators’ config in the YAML if both are supplied. Passing ‘none’ resets the config.
-t,--instance-type TEXTThe instance type to use. If specified, overrides the ‘resources.instance_type’ config. Passing ‘none’ resets the config.
--ports TEXTPorts to open on the cluster. If specified, overrides the ‘ports’ config in the YAML.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky serve update [OPTIONS] SERVICE_NAME SERVICE_YAML...d3x sky serve update --helpFunction
Update a SkyServe service.
Options
Option
Description
--workdir DIRECTORYIf specified, sync this dir to the remote working directory, where the task will be invoked. Overrides the ‘workdir’ config in the YAML if both are supplied.
--cloud TEXTThe cloud to use. If specified, overrides the ‘resources.cloud’ config. Passing ‘none’ resets the config.
--region TEXTThe region to use. If specified, overrides the ‘resources.region’ config. Passing ‘none’ resets the config.
--zone TEXTThe zone to use. If specified, overrides the ‘resources.zone’ config. Passing ‘none’ resets the config.
--num-nodes INTEGERNumber of nodes to execute the task on. Overrides the ‘num_nodes’ config in the YAML if both are supplied.
--cpus TEXTNumber of vCPUs each instance must have (e.g.,
--cpus=4(exactly 4) or--cpus=4+(at least 4)). This is used to automatically select the instance type.--memory TEXTAmount of memory each instance must have in GB (e.g.,
--memory=16(exactly 16GB),--memory=16+(at least 16GB))--disk-size INTEGEROS disk size in GBs.
--disk-tier [low|medium|high|best|none]OS disk tier. Could be one of low, medium, high, best, none. If best is specified, use the best possible disk tier. If none is specified, enforce to use default value and override the option in task YAML. Default: medium
--use-spot / --no-use-spotWhether to request spot instances. If specified, overrides the ‘resources.use_spot’ config.
--image-id TEXTCustom image id for launching the instances. Passing ‘none’ resets the config.
--env-file DOTENV_VALUESPath to a dotenv file with environment variables to set on the remote node.
--env _PARSE_ENV_VAREnvironment variable to set on the remote node. It can be specified multiple times. Examples: 1.
--env MY_ENV=1: set$MY_ENVon the cluster to be 1. 2.--env MY_ENV2=$HOME: set$MY_ENV2on the cluster to be the same value of$HOMEin the local environment where the CLI command is run. 3.--env MY_ENV3: set$MY_ENV3on the cluster to be the same value of$MY_ENV3in the local environment.--gpus TEXTType and number of GPUs to use. Example values: ‘V100:8’, ‘V100’ (short for a count of 1), or ‘V100:0.5’ (fractional counts are supported by the scheduling framework). If a new cluster is being launched by this command, this is the resources to provision. If an existing cluster is being reused, this is seen as the task demand, which must fit the cluster’s total resources and is used for scheduling the task. Overrides the ‘accelerators’ config in the YAML if both are supplied. Passing ‘none’ resets the config.
-t,--instance-type TEXTThe instance type to use. If specified, overrides the ‘resources.instance_type’ config. Passing ‘none’ resets the config.
--ports TEXTPorts to open on the cluster. If specified, overrides the ‘ports’ config in the YAML.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky serve status [OPTIONS] [SERVICE_NAMES]...d3x sky serve status --helpFunction
Show statuses of SkyServe services.
Options
Option
Description
-a,--allShow all information in full.
--endpointShow service endpoint.
-h,--helpShow help for the command..
Usage
d3x sky serve down [OPTIONS] [SERVICE_NAMES]...d3x sky serve down --helpFunction
Teardown service(s).
Options
Option
Description
-a,--allTear down all services.
-p,--purgeTear down services in failed status.
-y,--yesSkip confirmation prompt.
-h,--helpShow help for the command..
Usage
d3x sky serve logs [OPTIONS] SERVICE_NAME [REPLICA_ID]d3x sky serve logs --helpFunction
Tail the log of a service.
Options
Option
Description
--follow / --no-followFollow the logs of the job. [default: –follow] If –no-follow is specified, print the log so far and exit.
--controllerShow the controller logs of this service.
--load-balancerShow the load balancer logs of this service.
-h,--helpShow help for the command..
d3x umount¶
Usage
d3x umount [OPTIONS] MOUNTPATHd3x umount --helpFunction
Unmount bucket previously mounted using
d3x mountcommand.Options
Option
Description
--helpShow help for the command..
d3x version¶
Usage
d3x version [OPTIONS]d3x version --helpFunction
Show DKubeX version.
Options
Option
Description
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
d3x ws¶
Usage
d3x ws [OPTIONS] COMMAND [ARGS]...d3x ws --helpFunction
Commands related to DKubeX workspace.
Options
Option
Description
--helpShow this message and exit.
Commands
Command
Description
codeStart local VSCode and connect to D3X workspace
listList d3x workspaces
optunaGroup for optuna commands.
port-forwardForward port from workspace to local computer
resetreset given workspace to default image
scpCOPY files(s)/directory from/to D3X workspace
sshSSH to D3X workspace
ssh-copy-idCopy ssh public key to D3X user’s home
startStart given workspace
start-appStart given workspace app
stopStop given workspace
stop-appStop given workspace App
tensorboardGroup for tensorboard commands.
vncVNC connection to D3X workspace
Usage
d3x ws code [OPTIONS] WORKSPACE_NAMEd3x ws code --helpFunction
Start local VSCode and connect to D3X workspace.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command.
Usage
d3x ws list [OPTIONS]d3x ws list --helpFunction
List d3x workspaces.
Options
Option
Description
-a,--alllist workspaces including shared users
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow help for the command..
Usage
d3x ws optuna [OPTIONS] COMMAND [ARGS]...d3x ws optuna --helpFunction
Group for optuna commands.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
get-dbGetting db path for optuna
set-dbSetting db for optuna app inside workspace
Usage
d3x ws optuna get-db [OPTIONS]d3x ws optuna get-db --helpFunction
Getting db path for optuna
Options
Option
Description
-w,--workspace TEXTWorkspace name if it is not default workspace
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow this message and exit.
Usage
d3x ws optuna set-db [OPTIONS] DBd3x ws optuna set-db --helpFunction
Setting db for optuna app inside workspace
Options
Option
Description
-w,--workspace TEXTWorkspace name if it is not default workspace
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow this message and exit.
Usage
d3x ws port-forward [OPTIONS] WORKSPACE_NAME PORTd3x ws port-forward --helpFunction
Forward port from workspace to local computer.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..
Usage
d3x ws reset [OPTIONS] WORKSPACE_NAMEd3x ws reset --helpFunction
reset given workspace to default image.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..
Usage
d3x ws scp [OPTIONS] SOURCE DESTd3x ws scp --helpFunction
COPY files(s)/directory from/to D3X workspace.
Options
Option
Description
--helpShow help for the command..
Usage
d3x ws ssh [OPTIONS] WORKSPACE_NAMEd3x ws ssh --helpFunction
SSH to D3X workspace.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..
Usage
d3x ws ssh-copy-id [OPTIONS] WORKSPACE_NAMEd3x ws ssh-copy-id --helpFunction
Copy ssh public key to D3X user’s home.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..
Usage
d3x ws start [OPTIONS] WORKSPACE_NAMEd3x ws start --helpFunction
Start given workspace.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..
Usage
d3x ws start-app [OPTIONS] WORKSPACE_NAME APP_NAMEd3x ws start-app --helpFunction
Start given workspace app.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..
Usage
d3x ws stop [OPTIONS] WORKSPACE_NAMEd3x ws stop --helpFunction
Stop given workspace.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..
Usage
d3x ws stop-app [OPTIONS] WORKSPACE_NAME APP_NAMEd3x ws stop-app --helpFunction
Stop given workspace App.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..
Usage
d3x ws tensorboard [OPTIONS] COMMAND [ARGS]...d3x ws tensorboard --helpFunction
Group for tensorboard commands.
Options
Option
Description
--helpShow help for the command..
Commands
Command
Description
get-logdirGetting log directory for tensorboard
set-logdirSetting log directory for tensorboard app inside workspace
Usage
d3x ws tensorboard get-logdir [OPTIONS]d3x ws tensorboard get-logdir --helpFunction
Getting log directory for tensorboard
Options
Option
Description
-w,--workspace TEXTWorkspace name if it is not default workspace
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow this message and exit.
Usage
d3x ws tensorboard set-logdir [OPTIONS] LOGDIRd3x ws tensorboard set-logdir --helpFunction
Setting log directory for tensorboard app inside workspace
Options
Option
Description
-w,--workspace TEXTWorkspace name if it is not default workspace
-o,--output [yaml|json]Output format (supported- .json, .yaml)
--helpShow this message and exit.
Usage
d3x ws vnc [OPTIONS] WORKSPACE_NAMEd3x ws vnc --helpFunction
VNC connection to D3X workspace.
Options
Option
Description
-u,--user TEXTName of the workspace user.
--helpShow help for the command..