generated from databricks-industry-solutions/industry-solutions-blueprints
-
Notifications
You must be signed in to change notification settings - Fork 5
/
RUNME.py
139 lines (129 loc) · 6.36 KB
/
RUNME.py
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
# Databricks notebook source
# MAGIC %md This notebook sets up the companion cluster(s) to run the solution accelerator. It also creates the Workflow to illustrate the order of execution. Happy exploring!
# MAGIC 🎉
# MAGIC
# MAGIC **Steps**
# MAGIC 1. Simply attach this notebook to a cluster and hit Run-All for this notebook. A multi-step job and the clusters used in the job will be created for you and hyperlinks are printed on the last block of the notebook.
# MAGIC
# MAGIC 2. Run the accelerator notebooks: Feel free to explore the multi-step job page and **run the Workflow**, or **run the notebooks interactively** with the cluster to see how this solution accelerator executes.
# MAGIC
# MAGIC 2a. **Run the Workflow**: Navigate to the Workflow link and hit the `Run Now` 💥.
# MAGIC
# MAGIC 2b. **Run the notebooks interactively**: Attach the notebook with the cluster(s) created and execute as described in the `job_json['tasks']` below.
# MAGIC
# MAGIC **Prerequisites**
# MAGIC 1. You need to have cluster creation permissions in this workspace.
# MAGIC
# MAGIC 2. In case the environment has cluster-policies that interfere with automated deployment, you may need to manually create the cluster in accordance with the workspace cluster policy. The `job_json` definition below still provides valuable information about the configuration these series of notebooks should run with.
# MAGIC
# MAGIC **Notes**
# MAGIC 1. The pipelines, workflows and clusters created in this script are not user-specific. Keep in mind that rerunning this script again after modification resets them for other users too.
# MAGIC
# MAGIC 2. If the job execution fails, please confirm that you have set up other environment dependencies as specified in the accelerator notebooks. Accelerators may require the user to set up additional cloud infra or secrets to manage credentials.
# COMMAND ----------
# DBTITLE 0,Install util packages
# MAGIC %pip install git+https://github.com/databricks-academy/dbacademy@v1.0.13 git+https://github.com/databricks-industry-solutions/notebook-solution-companion@safe-print-html --quiet --disable-pip-version-check
# COMMAND ----------
from solacc.companion import NotebookSolutionCompanion
# COMMAND ----------
# MAGIC %md
# MAGIC
# MAGIC ## Set up secrets
# MAGIC Before setting up the rest of the accelerator, we need set up a few credentials in order to access Azure DevOps.
# MAGIC
# MAGIC Please follow the steps in the blog to create the Azure DevOps pipeline. Once the pipeline gets created in Azure DevOps, we will need to obtain an access token that we can use to trigger the pipeline from Databricks. Please follow these [steps](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows) to obtain the token. You will also need to obtain the name of the Azure DevOps Project, the Azure DevOps’s organization URL and the Pipeline ID.
# MAGIC
# MAGIC Here we demonstrate using the [Databricks Secret Scope](https://docs.databricks.com/security/secrets/secret-scopes.html) for credential management.
# MAGIC
# MAGIC Copy the block of code below, replace the name the secret scope and fill in the credentials and execute the block. After executing the code, The accelerator notebook will be able to access the credentials it needs.
# MAGIC
# MAGIC
# MAGIC ```
# MAGIC client = NotebookSolutionCompanion().client
# MAGIC try:
# MAGIC client.execute_post_json(f"{client.endpoint}/api/2.0/secrets/scopes/create", {"scope": "solution-accelerator-cicd"})
# MAGIC except:
# MAGIC pass
# MAGIC client.execute_post_json(f"{client.endpoint}/api/2.0/secrets/put", {
# MAGIC "scope": "solution-accelerator-cicd",
# MAGIC "key": "azure_devops_access_token",
# MAGIC "string_value": "____"
# MAGIC })
# MAGIC
# MAGIC client.execute_post_json(f"{client.endpoint}/api/2.0/secrets/put", {
# MAGIC "scope": "solution-accelerator-cicd",
# MAGIC "key": "azure_devops_organization_url",
# MAGIC "string_value": "____"
# MAGIC })
# MAGIC
# MAGIC client.execute_post_json(f"{client.endpoint}/api/2.0/secrets/put", {
# MAGIC "scope": "solution-accelerator-cicd",
# MAGIC "key": "azure_devops_pipeline_id",
# MAGIC "string_value": "____"
# MAGIC })
# MAGIC ```
# COMMAND ----------
job_json = {
"timeout_seconds": 28800,
"max_concurrent_runs": 1,
"tags": {
"usage": "solacc_testing",
"group": "MFG",
"accelerator": "edge-ml-for-manufacturing"
},
"tasks": [
{
"job_cluster_key": "edge_ml_cluster",
"notebook_task": {
"notebook_path": f"01_ML_Model_Trainer"
},
"task_key": "edge_ml_01"
},
{
"job_cluster_key": "edge_ml_cluster",
"notebook_task": {
"notebook_path": f"02_AZDevOps"
},
"task_key": "edge_ml_02",
"depends_on": [
{
"task_key": "edge_ml_01"
}
]
},
{
"job_cluster_key": "edge_ml_cluster",
"notebook_task": {
"notebook_path": f"04_MLFlow_Webhook_E2E_Test"
},
"task_key": "edge_ml_04",
"depends_on": [
{
"task_key": "edge_ml_02"
}
]
}
],
"job_clusters": [
{
"job_cluster_key": "edge_ml_cluster",
"new_cluster": {
"spark_version": "11.3.x-cpu-ml-scala2.12",
"spark_conf": {
"spark.databricks.delta.formatCheck.enabled": "false"
},
"num_workers": 2,
"node_type_id": {"AWS": "i3.xlarge", "MSA": "Standard_DS3_v2", "GCP": "n1-highmem-4"},
"custom_tags": {
"usage": "solacc_testing",
"group": "MFG",
"accelerator": "edge-ml-for-manufacturing"
},
}
}
]
}
# COMMAND ----------
dbutils.widgets.dropdown("run_job", "False", ["True", "False"])
run_job = dbutils.widgets.get("run_job") == "True"
NotebookSolutionCompanion().deploy_compute(job_json, run_job=run_job)