Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-stage pipeline + scoring observability #122

Merged
merged 16 commits into from
Dec 9, 2019

Conversation

algattik
Copy link
Contributor

@algattik algattik commented Dec 2, 2019

Builds on top of PR #121, and:

image

image

bump pip requirements versions (microsoft#104)
* Use Azure CLI tasks to remove need for variables SP_APP_ID, SP_APP_SECRET, SUBSCRIPTION_ID, TENANT_ID
* Updated gettin_started.md to point out variable path to artifact (microsoft#117)
* Made random hyperparameter (ridge regression alpha) a pipeline parameter, setting its value in the DevOps pipeline (microsoft#107)
* Changed unit test to test actual training code (partially solves microsoft#74)
* Fixed: attach_compute should set exit code after exception (microsoft#113)
* Fixed scoring endpoint HTTP behavior (microsoft#110)
* Fixed PipelineParameters format in call to Azure ML Extension (microsoft#118)
* Fixed Model build environment for Azure Web App for containers (microsoft#119)
Builds on top of PR microsoft#121, and:
- Replaces separate build + release pipelines with a single multi-stage pipeline with stages for Build, Train, ACI, AKS and Webapp deployment.
- ACI, AKS and Webapp deployment are optionally enabled (through Variables).
- Added example of custom traces (logging) and correlating traces with requests with Kusto queries.
- Added example of distributed tracing (client passes a trace header, logged by the scoring service).

![image](https://user-images.githubusercontent.com/22099722/69975882-52306580-1528-11ea-9705-65dc2ab737ea.png)
@dtzar dtzar self-assigned this Dec 6, 2019
Copy link
Member

@dtzar dtzar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@algattik So close on this after a bit of tweaking it with my commits. The only thing remaining is dynamically getting the MODEL_VERSION variable for when we deploy. Right now this build fails because it's looking for the hard-coded model version 1 in the variable template file while I have version 17 of the file, so it can't find it to deploy. IMO we should use the verify model registered script to return the model version for use in other steps.

@algattik
Copy link
Contributor Author

algattik commented Dec 7, 2019

Restored the pre-merge version where MODEL_VERSION is set by the verify_train_pipeline.py task.

@dtzar
Copy link
Member

dtzar commented Dec 9, 2019

image
Happy goodness, nice work!

@dtzar dtzar merged commit 2a22e75 into microsoft:master Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants