Jump to: navigation, search

Solum/SourceControlAsAService

< Solum
Revision as of 19:21, 15 May 2014 by Julien Vey (talk | contribs) (Created page with "= On-demand Source Control (or Source Control-as-a-Service) = This feature provides simple on-demand git repositories, tenant-aware, and ssh accessible. Note: We do not rely...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

On-demand Source Control (or Source Control-as-a-Service)

This feature provides simple on-demand git repositories, tenant-aware, and ssh accessible.

Note: We do not rely on gerrit or any other review system for now. We just provide git access to be able to host source code within Solum.

Use-case:

  • A user creates an application (solum app create) and specify in the plan file that he needs the creation of a git repository associated with this application.
  • Solum creates the git repository as a bare repository and return the url to the user
  • When the user creates an assembly associated with the plan, Solum add a hook to the repository associated with the trigger_url generated
  • The user either clones the repository or add it as a remote to an existing repository
  • When the user pushes code to the git repo, it triggers solum workflow

Implementation details:

  • Solum should rely on a tool like gitolite to provide git hosting.
  • It should also be coupled with OpenStack keypairs, so that a a keypair associated with an OpenStack tenant could be used for accessing a git repository createad by Solum.
  • Repositories would be hosted on a dedicated VM or a dedicated container spawned by Nova

Further investigations:

  • Do we need an API to provide “true” Source Control as-a-Service ? (julien: I don’t think we need it right now)