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

Typo and misc changes. #558

Merged
merged 2 commits into from
Jan 11, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/guides/launch/create-launch-job.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,12 @@ displayed_sidebar: default
---
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
import { CTAButtons } from '@site/src/components/CTAButtons/CTAButtons.tsx';


# Create a launch job


A job is a blueprint that contains contextual information about a W&B run it is created from; such as the run's source code, software dependencies, hyperparameters, artifact version, and so forth.

Once you have a launch job, you can add them to a pre-configured [launch queue](./launch-terminology.md#launch-queue). The launch agent that was deployed by you or someone on your team, will poll that queue and send the job (as a Docker image) to the compute resource that was configured on launch queue.
Expand All @@ -17,6 +20,8 @@ There are three ways to create a launch job:
* With a Docker image
* With Git repository

<CTAButtons colabLink="https://colab.research.google.com/drive/1wX0OSVxZJDHRsZaOaOEDx-lLUrO1hHgP"/>

The following sections show how to create a job based on each use case.


Expand Down
12 changes: 1 addition & 11 deletions docs/guides/launch/launch-faqs.md
Original file line number Diff line number Diff line change
Expand Up @@ -171,17 +171,7 @@ Yes. The suggested way is:

1. Add the secret as a vanilla k8s secret in the namespace where the runs will be created. something like `kubectl create secret -n <namespace> generic <secret_name> <secret value>`

2. Once that secret is created, you can specify a queue config to inject the secret when runs start. The end users cannot see the secret, only cluster admins can. An example is done in the `W&B Global CPU` queue:[https://wandb.ai/wandb/launch/UnVuUXVldWU6MTcxODMwOA==/config](https://wandb.ai/wandb/launch/UnVuUXVldWU6MTcxODMwOA==/config) . Specifically:

```yaml
env:
- name: OPENAI_API_KEY
valueFrom:
secretKeyRef:
key: password
name: openai-api-key

```
2. Once that secret is created, you can specify a queue config to inject the secret when runs start. The end users cannot see the secret, only cluster admins can.

### How can admins restrict what ML engineers have access to modify? For example, changing an image tag may be fine but other job settings may not be.

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/launch/launch-queue-observability.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
displayed_sidebar: default
---

# Queue monitoting dashboard (beta)
# Queue monitoring dashboard (beta)

Use the interactive **Queue monitoring dashboard** to view when a launch queue is in heavy use or idle, visualize workloads that are running, and spot inefficient jobs. The launch queue dashboard is especially useful for deciding whether or not you are effectively using your compute hardware or cloud resources.

Expand Down
1 change: 1 addition & 0 deletions docs/guides/launch/walkthrough.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
description: Getting started guide for W&B Launch.
displayed_sidebar: default
---
import { CTAButtons } from '@site/src/components/CTAButtons/CTAButtons.tsx';

# Walkthrough

Expand Down
Loading