Path1.Mod1.a - Explore ML Workspace - Setting Up Your Workspace Flashcards
O C R AMLDS AMLCO AMLRU
Six built in RBACs for controlling workspace access
- Owner
- Contributor - can’t grant access
- Reader - read only
- Azure ML Data Scientist - excludes create Compute or edit workspace settings
- Azure ML Compute Operator - can manage all Compute in the workspace
- Azure ML Registry User - Manages a Registry ie read/write/delete/promote Models in the Registry. Cannot create new or delete existing Registries
Sequence for creating an ML Service/Resource
The step that creates the ML Workspace
Log into Azure Portal
=> Azure Subscription
==> Create Resource Group
====> Create ML Service/Resource (to create the workspace)
=====> Auto-Created Resources
The four Azure Resources created when creating an ML Service/Resource
Azure Storage Account
Azure Key Vault
Azure Insights
Azure Container Registry
4 Ways to create a Workspace
- Azure Portal
- ARM Template
- Azure CLI
- Azure ML Python SDK
Study Code example; Describe what it does:
from azure.ai.ml.entities import Workspace workspace_name = "mlw-example" ws_basic = Workspace( name=workspace_name, location="eastus", display_name="Basic workspace-example", description="This example shows how to create a basic workspace", ) ml_client.workspaces.begin_create(ws_basic)
It creates a Workspace named “mlw-example” using the Python SDK, Region “East US”
TS E R, DA Dep ReCom
The three organizational setups for ML Solutions
Three common considerations between all three
Team Structure, Environment and Regional Setups
Data Access, Managing Deployment across Environments, Results Comparisons
Define Environment and give examples
“A collection of resources targeted by a deployment process, based on their stage in the application lifecycle”
Examples: Dev (Local), Test, QA, Staging, Production