Building an Azure Pipeline for Dataiku DSS with Project Deployer¶
In this article, we will show how to set up a sample CI/CD pipeline built on Azure for our Dataiku DSS project. This is part of a series of articles regarding CI/CD with Dataiku DSS.
For an overview of the topic and the initial configuration, please refer to the introductory article.
You can find all the files used in this project attached to this article dss_azure_pipeline-master.zip.
Based on the generic setup described in the introductory article, let’s review this case. We will be using a DSS feature called Project Deployer as the centerpiece for deployment.
Project Deployer is a feature released in version 9 of Dataiku DSS allowing you to centrally manage the deployment of bundles to Automation nodes.
If you are using a version lower than 9 or, for any reason, are not using Project Deployer, you should consult this article that deploys using direct connection to Automation nodes.
Our CI/CD environment will be using Azure DevOps as the orchestrator and the DSS servers themselves will run as Azure virtual machines.
Let’s start by presenting the different systems we need:
An Azure DevOps account with a project created (in our case, it will be called “dss-pipeline”). We have activated the Pipelines and Repos features (as we will host the code of the Azure pipeline in Azure itself).
One DSS Design node where data scientists will build their Flows, deployed in an Azure virtual machine.
Two DSS Automation nodes, one for pre-production and the other for production. They are also deployed as Azure virtual machines.
One simple Linux virtual machine configured as an Azure DevOps agent.
This article does not aim at explaining Azure DevOps or being a deep-dive on how to configure it. However, we will highlight the minimal setup needed to run this example, with links to the relevant Azure documentation:
On your project, you need to toggle on both the Pipelines & Repos features:
In order to execute your code, Azure needs to run it on a machine called an agent. For this example, we will need a self-hosted agent that can access our DSS virtual machines.
You will need to create a dedicated machine. It can be rather small (Standard_B2s in our example was more than enough), and follow the instructions in Deploy an Azure Pipelines agent on Linux - Azure Pipelines.
You also need to install Python 3.
In the end, you should see an online agent in the Agent pools of your Azure DevOps project.
You then need to create a Git repository in this project using Create a new Git repo in your project - Azure Repos. Once created, you can upload the content of this sample in it. The resulting repository should look like this:
Now that you have the repository configured, you can create a pipeline from it. In order to do that, go to the Pipelines section of your project, and click New pipeline.
In the next screen, you will need to indicate Azure DevOps which source code repository to use. Select the Git repository you have created just before. Lastly, you can change the parameters in the yaml file to match those of your platform. You can directly click run, and it should work!
As explained in the introductory article, we will use the DSS Prediction churn sample project that you need to have deployed and working on your Design node.
If you did not hit run right away, or even if you did and are wondering what this pipeline does, here is an overview.
The parameters are declared in the yaml file (they can be declared in other manners in Azure DevOps, but this approach is the simplest for a sample):
DSS_PROJECT (String): key of the project we want to deploy (e.g. DKU_CHURN)
DESIGN_URL (String): URL of the design node (e.g. http://10.0.0.4:1000)
DESIGN_API_KEY (Password): Personal API key to connect to this node. (This needs to be a personal API key; global API keys will not work).
AUTO_PREPROD_ID (String): ID of the pre-production node as known by Project Deployer (e.g. auto-uat)
AUTO_PREPROD_URL (String): URL of the PREPROD node (e.g. http://10.0.0.5:1000)
AUTO_PREPROD_API_KEY (Password): the API key to connect to this node
AUTO_PROD_ID (String): ID of the production node as known by Project Deployer (e.g. auto-prod)
AUTO_PROD_URL (String): URL of the PROD node (e.g. http://10.0.0.6:1000)
AUTO_PROD_API_KEY (Password):the API key to connect to this node
The pipeline contains 5 jobs, executed one after the other:
Let’s review those jobs one by one.
This stage is used to build a proper workspace. We need to ensure we are using the exact bundle ID across all our steps so we are computing it as a variable using a bash script.
The next step is to make sure the Python setup is correct, and then install all packages from the requirements.txt file.
Once done, our environment is ready to execute the good part.
This stage contains one Python script to validate that the project respects internal rules for being production-ready. We are using the Python Script task for that.
Any check can be performed at this stage, be it on the project structure, setup, or the coding parts, such as the code recipes or the project libraries.
We are using pytest capability to use command-line arguments by adding a conftest.py.
This is very specific to each installation, but here are the main takeaways:
In this project, we will be using the pytest framework to run the tests and the pytest-azurepipelines package that makes test reports available easily in Azure DevOps. The conftest.py is used to load our command line options. The run_test.py file contains the actual tests, all being Python functions starting with ‘TEST_’.
The checks we have: - There is at least one test DSS scenario (name starts with ‘TEST_’) and one named ‘TEST_SMOKE’. - Code complexity of Python recipes is in acceptable ranges. We are using radon for this (using pylint, flake8, or any other code inspection tool is of course also possible).
If this state is OK, we know we have a properly written project, and we can package it.
For archiving purposes, we are also pushing this file as part of Azure DevOps pipeline artifact by using the dedicated task PublishPipelineArtifact.
In this stage, we are deploying the bundle produced at the previous stage on our DSS PREPROD instance, and then running tests.
The bundle deployment is done in import_bundle.py:
We search if the project is already deployed or not. If it is deployed, we just update the bundle to use, and if it is not, we create a brand new deployment.
We request Project Deployer to deploy this new bundle using DSSProjectDeployerDeployment.start_update.
In this example, we consider connection mappings to be already valid as Project Deployer allows a default remapping to be defined at Infrastructure level, and this should cover most needs.
The following script run_test.py executes all the scenarios named TEST_XXX and fails if a result is not a success.
This pytest configuration has an additional twist. If you have only one test running all the TEST_XXX scenarios, they will be reported as a single test–successful or failed.
Here, we make this nicer by dynamically creating one unit test per scenario. In the final report, we will have one report per scenario executed, making the report more meaningful. This requires some understanding of pytest parameterization. Note that you can perfectly keep one test that will run all your scenarios if you are not feeling at ease with this.
The previous stage verified we have a valid package. It’s time to move it to production!
We have one Python script that deploys the bundle on the production Automation node, and then executes the TEST_SMOKE scenario. In case of failure, a rollback to the previous bundle is executed. In detail:
Same as for the pre-production deployment, we find or create a deployment on the production node (saving the currently running bundle id in case of update, for the rollback).
We ask Project Deployer to deploy the bundle.
In order to ensure the new bundle is working, we execute the TEST_SMOKE scenario.
If the deployment or TEST_SMOKE fails, we perform the rollback by re-deploying the previous bundle.
Executing the Pipeline¶
By default, Azure pipelines are executed after each commit in the repository. Alternatively, you can start it manually in the pipeline view by hitting the run button.
This is what you should see as the pipeline is being executed.
Once finished, you can also see the run results and the details on the tests.
And once executed, we can see those deployments within DSS in Project Deployer:
With this, you are done with this sample and can start tailoring it to your needs.