You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Change the `spec.template.spec.providerSpec.value.vmSize` to match the desired GPU instance type from Azure.
@@ -244,6 +244,12 @@ This section explains how to create the `nvidia-gpu-operator` namespace, set up
244
244
```bash
245
245
CHANNEL=$(oc get packagemanifest gpu-operator-certified -n openshift-marketplace -o jsonpath='{.status.defaultChannel}')
246
246
```
247
+
> [!NOTE]
248
+
> If your cluster was created without providing the pull secret, the cluster won't include samples or operators from Red Hat or from certified partners. This will result in the following error message:
249
+
>
250
+
> *Error from server (NotFound): packagemanifests.packages.operators.coreos.com "gpu-operator-certified" not found.*
251
+
>
252
+
> To add your Red Hat pull secret on an Azure Red Hat OpenShift cluster, [follow this guidance](howto-add-update-pull-secret.md).
247
253
248
254
1. Get latest Nvidia package using the following command:
Copy file name to clipboardExpand all lines: markdown templates/aml-templates/template-howto.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.author: your-msft-alias
10
10
author: your-github-account-name
11
11
ms.date: 04/10/2018
12
12
---
13
-
# This H1 is the title of the article. It appears in search, appears at the top of the article, and has the second greatest impact on search. 100 chars or less.
13
+
# This H1 is the title of the article. It appears in search, appears at the top of the article, and has the second most significant impact on search —100 chars or less.
Copy file name to clipboardExpand all lines: markdown templates/aml-templates/template-quickstart.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.date: 04/10/2018
12
12
---
13
13
14
14
# The H1 heading is the article title that shows on the web
15
-
Once sentence into intro about Machine Learning. Intro paragraph to explain the intent of this Quickstart, and time it takes. You can finish this Quickstart in about five minutes.
15
+
One sentence into the intro about Machine Learning. Intro paragraph to explain the intent of this Quickstart and the time it takes. You can finish this Quickstart in about five minutes.
16
16
17
17
If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
Server name |*example-name*|Choose a unique name that identifies your Azure Machine Learning server.
32
32
Subscription|*Your subscription*|The Azure subscription that you want to use for your server. If you have multiple subscriptions, choose the appropriate subscription in which the resource is billed for.
33
33
Resource Group|*myresourcegroup*| You may make a new resource group name, or use an existing one from your subscription.
34
-
Server admin login |*mylogin*| Make your own login account to use when connecting to the server.
34
+
Server admin login |*mylogin*| Make your login account when connecting to the server.
35
35
36
36
> [!IMPORTANT]
37
-
> The server admin login and password that you specify here are required to log in to the server and its databases later in this Quickstart. Remember or record this information for later use.
37
+
> The server admin login and password you specify here must log in to the server and its databases later in this Quickstart. Remember or record this information for later use.
38
38
39
39
## Example command using a bash shell comment
40
40
@@ -43,7 +43,7 @@ A code block you could use.
43
43
tool --switch1 value2 --switch2 value2
44
44
```
45
45
46
-
The table describes the switched used in the preceding command:
46
+
The table describes the switch used in the preceding command:
47
47
48
48
tool parameter |Suggested value|Description
49
49
---|---|---
@@ -60,17 +60,17 @@ Something happened.
60
60
61
61
62
62
## Clean up resources
63
-
Clean up the resources you created in the quickstart either by deleting the [Azure resource group](../../azure-resource-manager/resource-group-overview.md), which includes all the resources in the resource group, or by deleting the one server resource if you want to keep the other resources intact.
63
+
Clean up the resources you created in the Quickstart either by deleting the [Azure resource group](../../azure-resource-manager/resource-group-overview.md), which includes all the resources in the resource group, or by deleting the one server resource if you want to keep the other resources intact.
64
64
65
65
> [!TIP]
66
-
> Other Quickstarts in this collection build upon this quick start. If you plan to continue on to work with subsequent quickstarts, do not clean up the resources created in this quickstart. If you do not plan to continue, use the following steps to delete resources created by this quickstart in the Azure portal.
66
+
> Other Quickstarts in this collection build upon this quick start. If you plan to continue to work with subsequent quickstarts, do not clean up the resources created in this Quickstart. If you do not plan to continue, use the following steps to delete resources created by this Quickstart in the Azure portal.
67
67
68
-
To delete the entire resource group including the newly created server:
68
+
To delete the entire resource group, including the newly created server:
69
69
1. Locate your resource group in the Azure portal. From the left-hand menu in the Azure portal, click **Resource groups** and then click the name of your resource group, such as our example **myresourcegroup**.
70
-
2. On your resource group page, click **Delete**. Then type the name of your resource group, such as our example **myresourcegroup**, in the text box to confirm deletion, and then click **Delete**.
70
+
2. On your resource group page, click **Delete**. Then type the name of your resource group, such as our example **myresourcegroup**, in the text box to confirm the deletion, and then click **Delete**.
71
71
72
-
Or instead, to delete the newly created server:
73
-
1. Locate your server in the Azure portal, if you do not have it open. From the left-hand menu in Azure portal, click **All resources**, and then search for the server you created.
72
+
Or, instead, delete the newly created server:
73
+
1. Locate your server in the Azure portal if you do not have it open. From the left-hand menu in Azure portal, click **All resources**, and then search for the server you created.
74
74
2. On the **Overview** page, click the **Delete** button on the top pane.
# Tutorial: Verb ... --> This H1 is the title of the article. It appears in search, appears at the top of article, second greatest impact on search, 100 chars or less
14
+
# Tutorial: Verb ... --> This H1 is the title of the article. It appears in search, appears at the top of the article, and has the second greatest impact on search, 100 chars or less
15
15
16
-
AUTHORS: A singlesentence intro about AML. Intro paragraph to explain the intent of this tutorial. Lead with a light intro that describes, in customer-friendly language, what they’ll learn, or do, or accomplish. Answer the fundamental “why would I want to do this?” question. Avoid starting the tutorial with a bunch of notes or caveats.
16
+
AUTHORS: A single-sentence intro about AML. Intro paragraph to explain the intent of this tutorial. Lead with a light introduction that describes, in customer-friendly language, what they'll learn, or do, or accomplish. Answer the fundamental "why would I want to do this?" question. Avoid starting the tutorial with a bunch of notes or caveats.
17
17
18
-
In this tutorial you will do X...
18
+
In this tutorial, you will do X...
19
19
20
20
AUTHORS: Quick read tutorial [here](https://review.learn.microsoft.com/help/contribute/contribute-how-to-mvc-tutorial?branch=main). Also, don't forget to run Acrolinx to find issues before you commit.
21
21
22
-
In this tutorial, you use X to do Y or you learn how to:
22
+
In this tutorial, you use X to do Y, or you learn how to:
23
23
> [!div class="checklist"]
24
24
> * Create something
25
25
> * Do something
@@ -29,9 +29,9 @@ In this tutorial, you use X to do Y or you learn how to:
29
29
> [Important!]
30
30
> Avoid notes, tips, and important boxes. Except for this one, ha!
31
31
>
32
-
> Tutorials are typically longer and more complex than quickstarts. They are created from the list of top user tasks identified in milestone one and focus on the single best procedure for completing that task. A tutorial usually aligns to one or two customer tasks. At a minimum, you need one tutorial in the Tutorials node of the TOC.
32
+
> Tutorials are typically longer and more complex than quickstarts. They are created from the list of top user tasks identified in milestone one and focus on the best procedure for completing that task. A tutorial usually aligns with one or two customer tasks. At a minimum, you need one tutorial in the Tutorials node of the TOC.
33
33
>
34
-
> Tutorials are 100 – 200 level for an audience new to the service, product, or scenario. Ideally, your tutorials should build on each other using a common theme with the result being a completed customer scenario. Unlike how-to content, they are not open-ended, exhaustive walkthroughs of a feature.
34
+
> Tutorials are 100 – 200 for an audience new to the service, product, or scenario. Ideally, your tutorials should build on each other using a common theme, resulting in a completed customer scenario. Unlike how-to content, they are not open-ended, complete walkthroughs of a feature.
35
35
36
36
## Prerequisites
37
37
@@ -44,13 +44,13 @@ To complete this tutorial, you need:
44
44
## Log in to the Azure portal
45
45
Log in to the [Azure portal](https://portal.azure.com).
46
46
47
-
Don’t number H2 and H3 headings. Tutorials are procedurebased and customers understand that the sections follow in sequence.
47
+
Don't number H2 and H3 headings. Tutorials are procedure-based, and customers understand that the sections follow in sequence.
48
48
49
49
## Create a thing
50
50
Paragraphs here
51
51
52
52
Follow these steps to create the thing:
53
-
1. Click the **+ New** button found on the upper left-hand corner of the Azure portal.
53
+
1. Click the **+ New** button found in the upper left corner of the Azure portal.
Tutorials should always have a Next steps H2 that points to the next logical tutorial in a series (one link only here), or, if there are no other tutorials, to some other cool thing the customer can do with the service. Use the blue box format for tutorials and note that you can shorten the H1 in the boxes if the original one doesn’t fit.
71
+
Tutorials should always have a "Next steps" H2 that points to the following logical tutorial in a series (one link only here) or, if there are no other tutorials, to some other cool thing the customer can do with the service. Use the blue box format for tutorials, and note that you can shorten the H1 in the boxes if the original one doesn't fit.
72
72
73
73
> [!div class="nextstepaction"]
74
74
> [Azure Windows virtual machine tutorials](../../articles/machine-learning/overview-what-is-azure-ml.md)
75
75
76
-
Do not link to troubleshooting content or FAQs. This implies the customer is going to run into known issues. Either fix these issues beforehand or create a different path to success for users that avoid these problems.
76
+
Do not link to troubleshooting content or FAQs. This implies that the customer is going to run into known issues. Either fix these issues beforehand or create a different path to success for users that avoid these problems.
0 commit comments