<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Options :: MLOps v3 Accelerator</title><link>https://pgabriel-01.github.io/mlops-v3/options/index.html</link><description>Every option is a change to inputs.yaml followed by a regenerate, or a small edit to the generated files. This page shows which.&#10;How to change an option Edit inputs.yaml. Validate: Test-MLOpsAcceleratorInput -InputFile inputs.yaml. Regenerate over an existing project (commit first, then review the diff): Deploy-MLOpsAccelerator -InputFile inputs.yaml -OutputPath ./my-mlops -Upgrade Add -Deploy only if you also need to re-run the bootstrap (new repository, environments or identity). Changes to the workload and infrastructure are rolled out by the pipelines after you merge to main.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://pgabriel-01.github.io/mlops-v3/options/index.xml" rel="self" type="application/rss+xml"/><item><title>1 - Two environments</title><link>https://pgabriel-01.github.io/mlops-v3/options/01-two-environments/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/01-two-environments/index.html</guid><description>environments: [dev, prod] Any ordered subset of dev, test, prod; promotion and approvals follow the order. Each environment is a full workspace, so this roughly cuts the fixed cost by a third (see scenarios).&#10;Back to Options.</description></item><item><title>2 - Terraform or Bicep</title><link>https://pgabriel-01.github.io/mlops-v3/options/02-terraform-or-bicep/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/02-terraform-or-bicep/index.html</guid><description>iac: bicep # or terraform Both build on Azure Verified Modules and produce the same resources. The bootstrap (repository, identity and state storage) is always Terraform regardless of this setting.&#10;Back to Options.</description></item><item><title>3 - GitHub or Azure DevOps</title><link>https://pgabriel-01.github.io/mlops-v3/options/03-github-or-azure-devops/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/03-github-or-azure-devops/index.html</guid><description>cicd: github github_org: contoso github_repo: mlops-demo # or cicd: azdo azdo_org_url: https://dev.azure.com/contoso azdo_project: mlops Azure DevOps pipelines are generated under pipelines/ and must be registered manually (see Run).&#10;Back to Options.</description></item><item><title>4 - Your own data (ADLS)</title><link>https://pgabriel-01.github.io/mlops-v3/options/04-your-own-data-adls/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/04-your-own-data-adls/index.html</guid><description>data_source: adls adls: account_name: stcontosodata container: raw path: taxi/trips.csv # a CSV with the same columns as the taxi sample The datastore uses identity-based access; grant the workspace identity Storage Blob Data Reader (Grant-MLOpsStorageAccess does this). Snowflake and Azure SQL: land the data in ADLS first, see data sources.&#10;The adls source registers one file as a uri_file data asset, not an MLTable like the bundled samples. MLTable support for ADLS is deferred (see Known issues).</description></item><item><title>5 - Outbound allow-list</title><link>https://pgabriel-01.github.io/mlops-v3/options/05-outbound-allow-list/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/05-outbound-allow-list/index.html</guid><description>Scenario 3 only. The default allows pypi.org, files.pythonhosted.org, *.anaconda.com and conda.anaconda.org. Replace it with exactly what your environment needs:&#10;allowed_outbound_fqdns: - pypi.org - files.pythonhosted.org - internal-mirror.contoso.com Fewer hosts is safer, but training jobs that install packages fail if a host is missing.&#10;Back to Options.</description></item><item><title>6 - VNet address space</title><link>https://pgabriel-01.github.io/mlops-v3/options/06-vnet-address-space/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/06-vnet-address-space/index.html</guid><description>Scenario 4 only. Pick a range that does not overlap your corporate or hub networks:&#10;vnet_address_space: 10.20.0.0/16 Back to Options.</description></item><item><title>7 - Existing platform</title><link>https://pgabriel-01.github.io/mlops-v3/options/07-existing-platform/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/07-existing-platform/index.html</guid><description>Scenario 11 only. Supply IDs from your platform team; no network, DNS zones or Log Analytics are created:&#10;existing_platform: subnet_id: /subscriptions/.../subnets/snet-aml log_analytics_workspace_id: /subscriptions/.../workspaces/log-platform private_dns_zone_ids: blob: /subscriptions/.../privateDnsZones/privatelink.blob.core.windows.net # file, vault, acr, aml_api, aml_notebooks Back to Options.</description></item><item><title>8 - Budget alerts</title><link>https://pgabriel-01.github.io/mlops-v3/options/08-budget-alerts/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/08-budget-alerts/index.html</guid><description>budget_amount: 500 # USD per month, per environment resource group alert_emails: [mlops-team@contoso.com] Back to Options.</description></item><item><title>9 - Tags</title><link>https://pgabriel-01.github.io/mlops-v3/options/09-tags/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/09-tags/index.html</guid><description>tags: costcenter: "1234" owner: mlops-team Applied to every resource group and resource.&#10;Back to Options.</description></item><item><title>10 - Compute sizes</title><link>https://pgabriel-01.github.io/mlops-v3/options/10-compute-sizes/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/10-compute-sizes/index.html</guid><description>Set the VM size and the maximum node count in inputs.yaml, then regenerate. Check quota for the size in your region first.&#10;compute_vm_size: Standard_DS3_v2 compute_max_nodes: 4 The training cluster always scales down to 0 nodes. Instance counts for endpoints are not inputs; edit the generated files and commit your change after each -Upgrade review:&#10;What Setting Default Training cluster compute_vm_size and compute_max_nodes Standard_DS3_v2, 0 to 4 nodes Online endpoint compute_vm_size for the size; instance_count in mlops/azureml/online-deployment.yml Standard_DS3_v2, 1 Batch endpoint instance_count in mlops/azureml/batch-deployment.yml 1 Back to Options.</description></item><item><title>11 - Switch scenario</title><link>https://pgabriel-01.github.io/mlops-v3/options/11-switch-scenario/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/11-switch-scenario/index.html</guid><description>Change scenario and regenerate. Adding serving, a registry, a feature store or governance is a small change. Changing the network mode of an existing workspace is a bigger one and has not been tested; for anything beyond a trial, plan on a new workspace.&#10;Back to Options.</description></item><item><title>12 - Policy mode</title><link>https://pgabriel-01.github.io/mlops-v3/options/12-policy-mode/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/12-policy-mode/index.html</guid><description>policy_mode: audit # audit, deny or none Built-in Azure Policy guardrails on each environment resource group.&#10;audit (default): report non-compliance only. deny: block non-compliant changes. Try it in dev first. none: assign nothing. This is the default for scenario 11, where the platform team owns policy. See Azure Policy for the policies, the reasoning and the FAQ.&#10;Back to Options.</description></item><item><title>13 - CSV or parquet</title><link>https://pgabriel-01.github.io/mlops-v3/options/13-csv-or-parquet/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pgabriel-01.github.io/mlops-v3/options/13-csv-or-parquet/index.html</guid><description>Choose the bundled sample format with data_source:&#10;data_source: taxi-parquet # or taxi-csv (default) taxi-csv and taxi-parquet hold the same NYC taxi rows and register as MLTable data assets, so the pipeline code is identical.&#10;For real parquet, set data_source: nyc-taxi-open. It is a 2,000-row sample of the public Azure Open Datasets yellow taxi data (January 2015) with its original column names such as tpepPickupDateTime and fareAmount. prep.py cleans it and maps it to the model features. To train on more rows, copy parquet files from https://azureopendatastorage.blob.core.windows.net/nyctlc/yellow/ (anonymous read) into your ADLS container and read them with the adls source.</description></item></channel></rss>