Updated wording

Bobbins228 · Bobbins228 · commit 1b3d2736bf77 · 2024-04-05T10:14:50.000+01:00
diff --git a/demo-notebooks/additional-demos/hf_interactive.ipynb b/demo-notebooks/additional-demos/hf_interactive.ipynb
@@ -73,8 +73,7 @@
     "NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
     "The example here is a community image.\n",
     "\n",
-    "NOTE: By default the SDK uses Kueue as it's scheduling solution. \n",
-    "MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
+    "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
    ]
   },
   {
diff --git a/demo-notebooks/additional-demos/local_interactive.ipynb b/demo-notebooks/additional-demos/local_interactive.ipynb
@@ -38,8 +38,7 @@
     "NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
     "The example here is a community image.\n",
     "\n",
-    "NOTE: By default the SDK uses Kueue as it's scheduling solution. \n",
-    "MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
+    "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
    ]
   },
   {
diff --git a/demo-notebooks/guided-demos/0_basic_ray.ipynb b/demo-notebooks/guided-demos/0_basic_ray.ipynb
@@ -50,8 +50,7 @@
     "NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
     "The example here is a community image.\n",
     "\n",
-    "NOTE: By default the SDK uses Kueue as it's scheduling solution. \n",
-    "MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
+    "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
    ]
   },
   {
diff --git a/demo-notebooks/guided-demos/3_basic_interactive.ipynb b/demo-notebooks/guided-demos/3_basic_interactive.ipynb
@@ -47,7 +47,7 @@
     "NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
     "The example here is a community image.\n",
     "\n",
-    "NOTE: MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
+    "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
    ]
   },
   {
diff --git a/demo-notebooks/guided-demos/notebook-ex-outputs/0_basic_ray.ipynb b/demo-notebooks/guided-demos/notebook-ex-outputs/0_basic_ray.ipynb
@@ -50,8 +50,7 @@
     "NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
     "The example here is a community image.\n",
     "\n",
-    "NOTE: By default the SDK uses Kueue as it's scheduling solution. \n",
-    "MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
+    "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
    ]
   },
   {
@@ -90,7 +89,7 @@
    "id": "12eef53c",
    "metadata": {},
    "source": [
-    "Next, we want to bring our cluster up, so we call the `up()` function below to submit our Ray Cluster onto the queue, and begin the process of obtaining our resource cluster."
+    "Next, we want to bring our cluster up, so we call the `up()` function below to submit our cluster AppWrapper yaml onto the MCAD queue, and begin the process of obtaining our resource cluster."
    ]
   },
   {
@@ -358,7 +357,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.18"
+   "version": "3.9.undefined"
   },
   "vscode": {
    "interpreter": {
diff --git a/demo-notebooks/guided-demos/notebook-ex-outputs/1_basic_instascale.ipynb b/demo-notebooks/guided-demos/notebook-ex-outputs/1_basic_instascale.ipynb
@@ -5,7 +5,9 @@
    "id": "9865ee8c",
    "metadata": {},
    "source": [
-    "In this second notebook, we will go over the basics of using InstaScale to scale up/down necessary resources that are not currently available on your OpenShift Cluster (in cloud environments)."
+    "In this second notebook, we will go over the basics of using InstaScale to scale up/down necessary resources that are not currently available on your OpenShift Cluster (in cloud environments).\n",
+    "\n",
+    "NOTE: The InstaScale and MCAD components are in Tech Preview"
    ]
   },
   {
diff --git a/demo-notebooks/guided-demos/notebook-ex-outputs/3_basic_interactive.ipynb b/demo-notebooks/guided-demos/notebook-ex-outputs/3_basic_interactive.ipynb
@@ -5,7 +5,7 @@
    "id": "bbc21043",
    "metadata": {},
    "source": [
-    "In this fourth and final notebook, we will go over how to leverage the SDK to directly work interactively with a Ray cluster during development."
+    "In this notebook, we will go over how to leverage the SDK to directly work interactively with a Ray cluster during development."
    ]
   },
   {
@@ -47,7 +47,7 @@
     "NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
     "The example here is a community image.\n",
     "\n",
-    "NOTE: MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
+    "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
    ]
   },
   {
diff --git a/demo-notebooks/guided-demos/preview_nbs/0_basic_ray.ipynb b/demo-notebooks/guided-demos/preview_nbs/0_basic_ray.ipynb
@@ -50,8 +50,7 @@
     "NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
     "The example here is a community image.\n",
     "\n",
-    "NOTE: By default the SDK uses Kueue as it's scheduling solution. \n",
-    "MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
+    "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
    ]
   },
   {
diff --git a/demo-notebooks/guided-demos/preview_nbs/3_basic_interactive.ipynb b/demo-notebooks/guided-demos/preview_nbs/3_basic_interactive.ipynb
@@ -5,7 +5,7 @@
    "id": "bbc21043",
    "metadata": {},
    "source": [
-    "In this fourth and final notebook, we will go over how to leverage the SDK to directly work interactively with a Ray cluster during development."
+    "In this notebook, we will go over how to leverage the SDK to directly work interactively with a Ray Cluster during development."
    ]
   },
   {
@@ -47,7 +47,7 @@
     "NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
     "The example here is a community image.\n",
     "\n",
-    "NOTE: MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
+    "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
    ]
   },
   {

Original file line number	Diff line number	Diff line change
`@@ -73,8 +73,7 @@`
`73`	`73`	"NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
`74`	`74`	`"The example here is a community image.\n",`
`75`	`75`	`"\n",`
`76`		`- "NOTE: By default the SDK uses Kueue as it's scheduling solution. \n",`
`77`		- "MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
	`76`	+ "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
`78`	`77`	`]`
`79`	`78`	`},`
`80`	`79`	`{`
Original file line number	Diff line number	Diff line change
`@@ -38,8 +38,7 @@`
`38`	`38`	"NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
`39`	`39`	`"The example here is a community image.\n",`
`40`	`40`	`"\n",`
`41`		`- "NOTE: By default the SDK uses Kueue as it's scheduling solution. \n",`
`42`		- "MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
	`41`	+ "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
`43`	`42`	`]`
`44`	`43`	`},`
`45`	`44`	`{`
Original file line number	Diff line number	Diff line change
`@@ -50,8 +50,7 @@`
`50`	`50`	"NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
`51`	`51`	`"The example here is a community image.\n",`
`52`	`52`	`"\n",`
`53`		`- "NOTE: By default the SDK uses Kueue as it's scheduling solution. \n",`
`54`		- "MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
	`53`	+ "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
`55`	`54`	`]`
`56`	`55`	`},`
`57`	`56`	`{`
Original file line number	Diff line number	Diff line change
`@@ -47,7 +47,7 @@`
`47`	`47`	"NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
`48`	`48`	`"The example here is a community image.\n",`
`49`	`49`	`"\n",`
`50`		- "NOTE: MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
	`50`	+ "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
`51`	`51`	`]`
`52`	`52`	`},`
`53`	`53`	`{`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,9 @@`
`5`	`5`	`"id": "9865ee8c",`
`6`	`6`	`"metadata": {},`
`7`	`7`	`"source": [`
`8`		`- "In this second notebook, we will go over the basics of using InstaScale to scale up/down necessary resources that are not currently available on your OpenShift Cluster (in cloud environments)."`
	`8`	`+ "In this second notebook, we will go over the basics of using InstaScale to scale up/down necessary resources that are not currently available on your OpenShift Cluster (in cloud environments).\n",`
	`9`	`+ "\n",`
	`10`	`+ "NOTE: The InstaScale and MCAD components are in Tech Preview"`
`9`	`11`	`]`
`10`	`12`	`},`
`11`	`13`	`{`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,7 @@`
`5`	`5`	`"id": "bbc21043",`
`6`	`6`	`"metadata": {},`
`7`	`7`	`"source": [`
`8`		`- "In this fourth and final notebook, we will go over how to leverage the SDK to directly work interactively with a Ray cluster during development."`
	`8`	`+ "In this notebook, we will go over how to leverage the SDK to directly work interactively with a Ray cluster during development."`
`9`	`9`	`]`
`10`	`10`	`},`
`11`	`11`	`{`
`@@ -47,7 +47,7 @@`
`47`	`47`	"NOTE: We must specify the `image` which will be used in our RayCluster, we recommend you bring your own image which suits your purposes. \n",
`48`	`48`	`"The example here is a community image.\n",`
`49`	`49`	`"\n",`
`50`		- "NOTE: MCAD can be enabled over Kueue by using the `mcad=True` option in `ClusterConfiguration`"
	`50`	+ "NOTE: By default the SDK uses Kueue as it's scheduling solution to use MCAD set the `mcad=True` option in `ClusterConfiguration`"
`51`	`51`	`]`
`52`	`52`	`},`
`53`	`53`	`{`