use custom model

LICENCE

@@ -0,0 +1,21 @@
+Copyright (2022) Databricks, Inc.
+
+This library (the "Software") may not be used except in connection with the Licensee's use of the Databricks Platform Services pursuant to an Agreement (defined below) between Licensee (defined below) and Databricks, Inc. ("Databricks"). The Object Code version of the Software shall be deemed part of the Downloadable Services under the Agreement, or if the Agreement does not define Downloadable Services, Subscription Services, or if neither are defined then the term in such Agreement that refers to the applicable Databricks Platform Services (as defined below) shall be substituted herein for “Downloadable Services.” Licensee's use of the Software must comply at all times with any restrictions applicable to the Downlodable Services and Subscription Services, generally, and must be used in accordance with any applicable documentation. For the avoidance of doubt, the Software constitutes Databricks Confidential Information under the Agreement.
+
+Additionally, and notwithstanding anything in the Agreement to the contrary:
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+you may view, make limited copies of, and may compile the Source Code version of the Software into an Object Code version of the Software. For the avoidance of doubt, you may not make derivative works of Software (or make any any changes to the Source Code version of the unless you have agreed to separate terms with Databricks permitting such modifications (e.g., a contribution license agreement)).
+If you have not agreed to an Agreement or otherwise do not agree to these terms, you may not use the Software or view, copy or compile the Source Code of the Software.
+
+This license terminates automatically upon the termination of the Agreement or Licensee's breach of these terms. Additionally, Databricks may terminate this license at any time on notice. Upon termination, you must permanently delete the Software and all copies thereof (including the Source Code).
+
+Agreement: the agreement between Databricks and Licensee governing the use of the Databricks Platform Services, which shall be, with respect to Databricks, the Databricks Terms of Service located at www.databricks.com/termsofservice, and with respect to Databricks Community Edition, the Community Edition Terms of Service located at www.databricks.com/ce-termsofuse, in each case unless Licensee has entered into a separate written agreement with Databricks governing the use of the applicable Databricks Platform Services.
+
+Databricks Platform Services: the Databricks services or the Databricks Community Edition services, according to where the Software is used.
+
+Licensee: the user of the Software, or, if the Software is being used on behalf of a company, the company.
+
+Object Code: is version of the Software produced when an interpreter or a compiler translates the Source Code into recognizable and executable machine code.
+
+Source Code: the human readable portion of the Software.

NOTICE

@@ -0,0 +1,28 @@
+Copyright (2022) Databricks, Inc.
+## License
+This Software includes software developed at Databricks (https://www.databricks.com/) and its use is subject to the included LICENSE file.
+
+This Software contains code from the following open source projects, licensed under the Apache 2.0 license:
+
+psf/requests - https://github.com/psf/requests
+Copyright 2019 Kenneth Reitz
+
+## Data collection
+To improve users experience and dbdemos asset quality, dbdemos sends report usage and capture views in the installed notebook (usually in the first cell) and other assets like dashboards. This information is captured for product improvement only and not for marketing purpose, and doesn't contain PII information. By using `dbdemos` and the assets it provides, you consent to this data collection. If you wish to disable it, you can set `Tracker.enable_tracker` to False in the `tracker.py` file.
+
+## Resource creation
+To simplify your experience, `dbdemos` will create and start for you resources. As example, a demo could start (not exhaustive):
+- A cluster to run your demo
+- A Delta Live Table Pipeline to ingest data
+- A DBSQL endpoint to run DBSQL dashboard
+- An ML model
+
+While `dbdemos` does its best to limit the consumption and enforce resource auto-termination, you remain responsible for the resources created and the potential consumption associated.
+
+## Catalog/Database created
+dbdemos will try to create catalogs & databases (schemas). Demos are using the hive_metastore or UC catalogs. dbdemos will try to use the dbdemos catalog when possible.
+
+Permissions / ownership can be granted to all users (account users) in these datasets.
+
+## Support
+Databricks does not offer official support for `dbdemos` and the associated assets.

README.md

@@ -9,4 +9,232 @@ app_file: app.py
 pinned: false
 ---
 
-Check out the configuration reference at https://huggingface.co/docs/hub/spaces-config-reference
+# dbdemos
+
+DBDemos is a toolkit to easily install Lakehouse demos for Databricks.
+
+Simply deploy & share demos on any workspace. dbdemos is packaged with a list of demos:
+
+- Lakehouse, end-to-end demos (ex: Lakehouse Retail Churn)
+- Product demos (ex: Delta Live Table, CDC, ML, DBSQL Dashboard, MLOps...)
+
+**Please visit [dbdemos.ai](https://www.dbdemos.ai) to explore all our demos.**
+
+## Installation 
+**Do not clone the repo, just pip install dbdemos wheel:**
+
+```
+%pip install dbdemos
+```
+
+## Usage within Databricks
+
+See [demo video](https://drive.google.com/file/d/12Iu50r7hlawVN01eE_GoUKBQ4kvUrR56/view?usp=sharing) 
+```
+import dbdemos
+dbdemos.help()
+dbdemos.list_demos()
+
+dbdemos.install('lakehouse-retail-c360', path='./', overwrite = True)
+```
+
+![Dbdemos install](https://github.com/databricks-demos/dbdemos/raw/main/resources/dbdemos-screenshot.png)
+
+## Requirements
+
+`dbdemos` requires the current user to have:
+* Cluster creation permission
+* DLT Pipeline creation permission 
+* DBSQL dashboard & query creation permission
+* For UC demos: Unity Catalog metastore must be available (demo will be installed but won't work) 
+
+New with 0.2: dbdemos can import/export dahsboard without the import/export preview (using the dbsqlclone toolkit)
+
+## Features
+
+* Load demo notebooks (pre-run) to the given path
+* Start job to load dataset based on demo requirement
+* Start demo cluster customized for the demo & the current user
+* Setup DLT pipelines
+* Setup DBSQL dashboard
+* Create ML Model
+* Demo links are updated with resources created for an easy navigation
+
+## Feedback
+
+Demo not working? Can't use dbdemos? Please open a github issue. <br/>
+Make sure you mention the name of the demo.
+
+# DBDemos Developer options
+
+Read the following if you want to add a new demo bundle.
+
+## Packaging a demo with dbdemos
+
+Your demo must contain a `_resources` folder where you include all initialization scripts and your bundle configuration file.
+
+### Links & tags
+DBdemos will dynamically override the link to point to the resources created.
+
+**Always use links relative to the local path to support multi workspaces. Do not add the workspace id.**
+
+#### DLT pipelines:
+Your DLT pipeline must be added in the bundle file (see below).
+Within your notebook, to identify your pipeline using the id in the bundle file, specify the id `dbdemos-pipeline-id="<id>"`as following:
+
+`<a dbdemos-pipeline-id="dlt-churn" href="#joblist/pipelines/a6ba1d12-74d7-4e2d-b9b7-ca53b655f39d" target="_blank">Delta Live Table pipeline</a>`
+
+#### Workflows:
+Your workflows must be added in the bundle file (see below).
+Within your notebook, to identify your workflow using the id in the bundle file, specify the id `dbdemos-workflow-id="<id>"`as following:
+
+`<a dbdemos-workflow-id="credit-job" href="#joblist/pipelines/a6ba1d12-74d7-4e2d-b9b7-ca53b655f39d" target="_blank">Access your workflow</a>`
+
+
+#### DBSQL dashboards:
+DBSQL dashboard are automatically downloaded during the process. No need to add them in the bundle file. Simply use links as following:
+
+` <a href="/sql/dashboards/19394330-2274-4b4b-90ce-d415a7ff2130" target="_blank">Churn Analysis Dashboard</a>`
+
+
+
+### bundle_config
+The demo must contain the a `./_resources/bundle_config` file containing your bundle definition.
+This need to be a notebook & not a .json file (due to current api limitation).
+
+```json
+{
+  "name": "<Demo name, used in dbdemos.install('xxx')>",
+  "category": "<Category, like data-engineering>",
+  "title": "<Title>.",
+  "description": "<Description>",
+  "bundle": <Will bundle when True, skip when False>,
+  "tags": [{"dlt": "Delta Live Table"}],
+  "notebooks": [
+    {
+      "path": "<notebbok path from the demo folder (ex: resources/00-load-data)>", 
+      "pre_run": <Will start a job to run it before packaging to get the cells results>, 
+      "publish_on_website": <Will add the notebook in the public website (with the results if it's pre_run=True)>, 
+      "add_cluster_setup_cell": <if True, add a cell with the name of the demo cluster>,
+      "title":  "<Title>", 
+      "description": "<Description (will be in minisite also)>",
+      "parameters": {"<key>": "<value. Will be sent to the pre_run job>"}
+    }
+  ],
+  "init_job": {
+    "settings": {
+        "name": "demos_dlt_cdc_init_{{CURRENT_USER_NAME}}",
+        "email_notifications": {
+            "no_alert_for_skipped_runs": False
+        },
+        "timeout_seconds": 0,
+        "max_concurrent_runs": 1,
+        "tasks": [
+            {
+                "task_key": "init_data",
+                "notebook_task": {
+                    "notebook_path": "{{DEMO_FOLDER}}/_resources/01-load-data-quality-dashboard",
+                    "source": "WORKSPACE"
+                },
+                "job_cluster_key": "Shared_job_cluster",
+                "timeout_seconds": 0,
+                "email_notifications": {}
+            }
+        ]
+        .... Full standard job definition
+    }
+  },
+  "pipelines": <list of DLT pipelines if any>
+  [
+    {
+      "id": "dlt-cdc", <id, used in the notebook links to go to the generated notebook: <a dbdemos-pipeline-id="dlt-cdc" href="#joblist/pipelines/xxxx">installed DLT pipeline</a> >
+      "run_after_creation": True,
+      "definition": {
+        ... Any DLT pipelineconfiguration...
+        "libraries": [
+            {
+                "notebook": {
+                    "path": "{{DEMO_FOLDER}}/_resources/00-Data_CDC_Generator"
+                }
+            }
+        ],
+        "name": "demos_dlt_cdc_{{CURRENT_USER_NAME}}",
+        "storage": "/demos/dlt/cdc/{{CURRENT_USER_NAME}}",
+        "target": "demos_dlt_cdc_{{CURRENT_USER_NAME}}"
+      }
+    }
+  ],
+  "workflows": [{
+    "start_on_install": False,
+    "id": "credit-job",
+    "definition": {
+        "settings": {
+        ... full pipeline settings
+    }
+  }]  
+}
+```
+
+dbdemos will replace the values defined as {{<KEY>}} based on who install the demo. Supported keys:
+* TODAY
+* CURRENT_USER (email)
+* CURRENT_USER_NAME (derivated from email)
+* DEMO_NAME
+* DEMO_FOLDER
+
+
+# DBDemo Installer configuration
+
+The following describe how to package the demos created.
+
+The installer needs to fetch data from a workspace & start jobs. To do so, it requires informations `local_conf.json`
+```json
+{
+  "pat_token": "xxx",
+  "username": "xx.xx@databricks.com",
+  "url": "https://xxx.databricks.com",
+  "repo_staging_path": "/Repos/xx.xx@databricks.com",
+  "repo_name": "<field-demos_build>",
+  "repo_url": "https://github.com/<repo containing demos to package>",
+  "branch": "master",
+  "current_folder": "<Used to mock the current folder outside of a notebook, ex: /Users/quentin.ambard@databricks.com/test_install_demo>"
+}
+```
+
+### Creating the bundles:
+```python
+bundler = JobBundler(conf)
+# the bundler will use a stating repo dir in the workspace to analyze & run content.
+bundler.reset_staging_repo(skip_pull=False)
+# Discover bundles from repo:
+bundler.load_bundles_conf()
+# Or manually add bundle to run faster:
+#bundler.add_bundle("product_demos/Auto-Loader (cloudFiles)")
+
+# Run the jobs (only if there is a new commit since the last time, or failure, or force execution)
+bundler.start_and_wait_bundle_jobs(force_execution = False)
+
+packager = Packager(conf, bundler)
+packager.package_all()
+```
+
+
+## Licence
+See LICENSE file.
+
+## Data collection
+To improve users experience and dbdemos asset quality, dbdemos sends report usage and capture views in the installed notebook (usually in the first cell) and dashboards. This information is captured for product improvement only and not for marketing purpose, and doesn't contain PII information. By using `dbdemos` and the assets it provides, you consent to this data collection. If you wish to disable it, you can set `Tracker.enable_tracker` to False in the `tracker.py` file.
+
+## Resource creation
+To simplify your experience, `dbdemos` will create and start for you resources. As example, a demo could start (not exhaustive):
+- A cluster to run your demo
+- A Delta Live Table Pipeline to ingest data
+- A DBSQL endpoint to run DBSQL dashboard
+- An ML model
+
+While `dbdemos` does its best to limit the consumption and enforce resource auto-termination, you remain responsible for the resources created and the potential consumption associated.
+
+## Support
+Databricks does not offer official support for `dbdemos` and the associated assets.
+For any issue with `dbdemos` or the demos installed, please open an issue and the demo team will have a look on a best effort basis.
+

app.py

@@ -40,9 +40,11 @@ demo = gr.ChatInterface(
     chatbot=gr.Chatbot(height=400),
     textbox=gr.Textbox(placeholder="Ask me a question",
                        container=False, scale=7),
-    title="Chat with a Databricks LLM serving endpoint",
-    description="This is an advanced model hosted on Databricks Serving.",
-    examples=[["Hello"], ["What is MLflow?"], ["What is Apache Spark?"]],
+    title=""Databricks LLM RAG demo - Chat with llama2 Databricks model serving endpoint,
+    description="This chatbot is a demo example for the dbdemos llm chatbot
+This content is provided as a LLM RAG educational example, without support. It is using llama2, can hallucinate and should not be used as production content.
+Please review our dbdemos license and terms for more details.",
+    examples=[["How can I start a Databricks cluster?"]],
     cache_examples=False,
     theme="soft",
     retry_btn=None,