Solum/FeatureBlueprints/GitIntegration
Blueprint: https://blueprints.launchpad.net/solum/+spec/git-integration
Git Deployment
Functionality
A deployment unit (DU) is a unit of deployment for the application being deployed. For example, if Solum is configured to use containers for deploying application code, then the a DU would refer to a container instance.
As an application developer, I want to push my code to my git repository, and have the platform automatically detect the code push and generate a running application using the new code.
I would be able to use git push for deploying a new application, or to update an existing application.
I would be able to specify the application characteristics (AppName, size and number of deployment units, auto scale policies, etc) while deploying my app.
Following are the application characteristics that can be specified (this is an indicative list, not intended to be a comprehensive list).
Application Characteristics
| Attribute name | Description | Required? |
|---|---|---|
| DU Count | Initial number of deployment units. | Optional (default = 1) |
| Flavor | Size of each DU (as determined by RAM, CPU, disk space, allocated to each DU). Small, medium, large, extra large, etc. the sizing characteristics of what is small and what is large is configurable by the platform service provider | Optional (if no flavor is provided, then a default flavor will be used. The default flavor is configurable by the service provider) |
| AutoScale | Should the application auto-scale (Y/N) | Optional (default = N) |
| MinInstances | Minimum number of DU's (lower threshold for the auto scale policy) | Optional (default = 1) |
| MaxInstances | Maximum number of DU's (upper threshold for the auto scale policy) | Optional (default = specified DU Count during app creation) |
| ShellEnvironment | Set application specific shell environment variables at app start up | Optional |
| LanguagePack | User could specify the language pack (say MyPythonPack) to be used during app creation. If no language pack is specified, then the platform would auto-detect the default language pack associated with the code being pushed. | Optional |
| Services | List of services that the application will bind to (e.g.Trove, NewRelic). The services list would also optionally contain any service initialization parameters if the service support it. An example of this will be an SQL script passed to a database service to create the custom application scheme. | Optional |
The general workflow for a git based deployment is as follows:
1. Precondition: the user is already registered as an OpenStack user, and has been associated with the Solum service (see the blueprint "authentication" for details)
2. RegisterApp: registers the new application with Solum (generates a git repository in Solum and associates it with the new app).
- Inputs: AppName (Optional), if no AppName is provided, Solum will generate one
- Returns: URL of the remote git repository, and the URL associated with the app
3. Git push (deploys and generates a running app). Builds the app binary from source. Git push will use the default application characteristics (per the default values specified in the Application Characteristics table above). The default values can be overridden by specifying the values in an application meta-data file that is stored along with the application source.
Solum will implement Environments/Application Life Cycle management as part of the roadmap. However, implementation of environments is out of scope of this blueprint.
