Introduction

ModelOp Center allows integration with Git platforms in order to externalize the management of model assets as well as allow for a distributed development of such resources. This integration allows for the development of such assets to be done from the platform (IDE) of choice of the Data Scientist providing greater flexibility using a widely accepted technology such as Git.

ModelOp Center allows different configured levels of interaction with Git:

No Git interaction: Model assets are not stored in a Git repository but rather are stored in a local database.
Local Git repository: It is possible to create and work in a local Git repository within ModelOp Center where changes to the asset will be committed changes. A remote git repository can be added to the asset at any point.
Remote Git repository. It is also possible to configure a remote git repository to sync external changes back into ModelOp Center working directory. A configuration option controls whether the commits in the repo are pushed to the remote.

Remote import

Given a remote repository url to clone, ModelOp Center clones down the repo and creates a “Model” with all files represented as assets within it. All non-source files are imported as external assets and loaded into the configured external file asset repository instance (e.g. S3 / MinIO). All source assets will be loaded into the “Model” instance, and have their repository information loaded appropriately.

Source files are automatically determined (by file extension):
- Model source: ".py", ".py3", ".c", ".r", ".pfa", ".ipynb", ".ppfa", ".java", ".m"
- Test result comparator: ".dmn", ".cmmn"
Non-source files are considered any other type of files.

ModelOp Center allows to import a git repository through ModelOp Center Dashboard

Click on the “Models” menu item.
On the top right corner click on “Import”.
Provide the details of the “Remote Repository Url” and “Branch”.
Please note for the URL to extract the one depending on your Git platform, generally you can find this URL by going to the “Clone” button and selecting the “HTTPS clone” option.
Click on “Import model from Git”

Note: these steps assume the repository is public without authentication. The following sections detail how to configure the integration when authentication is required.

Git Integration

In order to integrate authenticated remote repository, ModelOp Center will need to be configured to utilize a Service Account to pull from the specified repository. This Service Account should be able to read and/ or write for the repositories to imported and integrated with ModelOp Center.

Git Credentials

The username and password to integrate with the Git repository are set as properties in the container definition for model-manager. These can be obscured using Kubernetes Secrets or other existing credential management systems.

model-manage.git.username=<The git username>
model-manage.git.password=<The username's passphrase>

The above configuration will be used to access all remote repositories from ModelOp Center, which requires the Service Account be added to integrated repositories.

Local Repository Settings

ModelOp Center also provides additional parameters to configure the behavior of the local repository.

Container: "model-manager":

model-manage.repo.push=false   # Enable/Disable to push back to the remote repository after an update has been applied to an asset in ModelOp Center
model-manage.repo.change-poll-rate=120000   # Time interval between remote repository polls for updates.
model-manage.repo.base-directory=/tmp/model-manage-repos   # Default container's base for git repositories

Git Config

It is possible to add git-specific configurations to control how ModelOp Center’s git repository behaves. Please refer to git scm for more details on the git configuration and how it can be used to achieve certain behavior.

Useful git config syntax terminology for the purposes of mapping git configuration into ModelOp Center

Assume a property key of the form 'section.subsection.variable=value', the following is used as guideline:

A section is considered to be everything up to the first dot of the param key.
A subsection is considered everything in between the first and the last dots of the param key. This is optional and may be null if the key contains only one dot (i.e. 'section.variable' as opposed to 'section.subsection.variable')
A variable name is considered everything from the last dot onwards.
A variable value is the param value itself. Repeated values are ok and are considered multivars in gitconfig. These should be presented in yaml as list or its equivalent properties (key.1, key.2).

See more about gitconfig syntax here.

The idea behind ModelOp Center’s git config customization is that any git config variable can be mapped in the following way.

The example desired git config file being the following:

  [http]
    sslVerify = true
  [http "https://example.com/scm/demo/repo.git"]
    sslVerify = false
  [format]
    notes = foo
    notes = bar

Then the expected ModelOp Center configuration would be the following:

Container: "model-manager"
  model-manage.git.config.http.sslVerify=true
  model-manage.git.config.http.https://example.com/scm/demo/repo.git.sslVerify=false
  model-manage.git.config.format.notes.0=foo
  model-manage.git.config.format.notes.1=bar

Please refer to git-scm for more comprehensive list of variables that can be set through git config.

Load on startup DEMO ONLY

Model Manage can configured to automatically import repositories upon startup. This is mainly used for demo purposes.

  model-manage.git.load-on-startup.repos.0.repositoryRemote="https://github.com/modelop/first-repo.git"
  model-manage.git.load-on-startup.repos.0.repositoryBranch="master"
  model-manage.git.load-on-startup.repos.1.repositoryRemote="https://github.com/modelop/second-repo.git"
  model-manage.git.load-on-startup.repos.1.repositoryBranch="master"
  ...

View Asset Git Details

ModelOp Center provides multiple ways to see the details of the git integration for various assets.

ModelOp Center Dashboard

The model’s assets repository configuration can be seen within the ModelOp Center Dashboard.

Click on the “Models” menu item.
From the list on the main panel, select the desired model to inspect.
From the sub-menus on the left, click on “<> Sources”
On the main panel, select the “Metadata” tab on the title
On the left panel, you can inspect the various source files as needed.

Jupyter Notebook Plugin

Git configuration is available directly within a Notebook via the Jupyter Notebook Plugin. When registering or opening a model, these details are available in the “View” button, a ModelOp specific Cell Toolbar button.

Within the Jupyter Notebook, click on the menu “View”.
Click on “Cell Toolbar”.
Select the “ModelOp Model” toolbar option.
On the desired model asset (cell) click on the toolbar button “Asset Details”. This button will be visible for ModelOp registered models only.
1. If the selected asset does not have repository configured previously, it will allow the user to configure it.
2. If the selected asset already had a repository configured, these values can be modified as well.

v2.1 Integrate with Git