GitLab Duo License Management for Self-Hosted Model Deployments

GitLab Duo License Management

The Self-Managed GitLab Rails will self-issue a token (same process as for Gitlab.com) that the local AI Gateway can verify, to guarantee that cross-service communication is secure.

The following discussion from !148599 (merged) should be addressed:

• @jessieay started a discussion: (+5 comments)

  Hi @sean_carroll !

  Nicely done, I left some small questions/suggestions.

  One element I do not see addressed here is authentication/authorization. Right now, that is handled by Cloud Connector. But in an airgapped environment we would not be able to access cloud.gitlab.com to tell us if a user has the correct subscription/access. Blueprints don't require that every element of the technical solution has been thought through, but do you think that those are points worth addressing in this blueprint?

This has already been discussed at length in this thread and this thread

Sync calls

• Notes from 2024-05-05 sync call.