Skip to main content

Integration and Provisioning User Glossary

Integration and Provisioning relate to the Provisioner module and adjacent extensions which have the objective of coordinating the deployment of data projects as atomic deployment units, and integrating Witboost with the Data plane of you organization.

Deployment​

Deployment, also expressed as provisioning, is the process where a particular version of a project is released and published on a specific environment. This process includes the provisioning of the project's system and set of components as a deployment unit, publication on the Market Plane and more, all in an atomic process. You can find more information about deployment here and the reference documentation.

Deployment Unit​

A Deployment Unit is the main concept driving the Provisioner module. It refers to a system, optionally composed of one or more child components, that can be deployed/provisioned within a target infrastructure. The deployment of a Deployment Unit is composed of a set of tasks with dependencies among them that specify the order these components are deployed. In order to deploy on a target infrastructure of the Data Plane, the Provisioner module contacts the configured Tech Adapter for a specific component sending it the deployment unit metadata and receiving the outcome of the provision task.

Dependencies​

Dependencies of a Deployment Unit are defined following the dependsOn field on the descriptor of each component. It defines a list of identifiers of other components that need to be correctly deployed first before the deployment of said component can start. The deployment of all components inherently depend on the correctly deployment of the system, which is always the first to be deployed.

Components without dependencies are concurrently deployed, and if the deployment of one component fails, the whole deployment process is marked as Corrupted and downstream components are not deployed.

Release status​

The status of the release of a specific deployment in a particular environment. It can take different values like NOT DEPLOYED, CORRUPT, DEPLOYED, PARTIALLY DEPLOYED, IN PROGRESS. For more information check out this section of the documentation.

Undeployment​

Undeployment is the opposite action of deployment, where resources are unprovisioned from the target infrastructure and unpublished from the Market Plane. It is also possible to specify a Remove Data flag that the Tech Adapter can interpret in order to remove data along with the previously deployed resources.

Tech Adapter​

Deployment of components that target a infrastructure in the Data Plane and expects the creation of resources in said infrastructure do it so through a Tech Adapter, a microservice configured by the Platform Team to take as input the descriptor of the Deployment Unit and deployed the necessary entities said component model, be tables, pipelines, streams, machine learning models, etc.

Tech Adapters are also in charge of component validation along with the Witboost Computational Governance, plus undeployment, reverse provisioning, and access control grant for consumables.