Difference between revisions of "Solum/FeatureBlueprints/DeployApp"
< Solum
(→Functionality) |
(→Functionality) |
||
| Line 45: | Line 45: | ||
| 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 pick the default language pack associated with the code being pushed. || 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 pick 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 a SQL script passed to a database service to create the custom application scheme. | + | | 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 a SQL script passed to a database service to create the custom application scheme. || Optional |
|- | |- | ||
|} | |} | ||
=== Implementation === | === Implementation === | ||
Revision as of 20:30, 6 October 2013
Solum-R1.1 Deploy application
Functionality
===== Generic note on Solum's User Interface =====
Solum exposes its "user interface" via the following mechanisms:
- REST API
- CLI interface
- GIT
- a set of SDK's in various languages
- UI Console
The CLI, GIT, SDK's and the UI console are ease of use interfaces that are layered on top of the REST API. User can also directly call into the REST API.
===== End Generic Note =====
As an application developer, I can invoke a REST API call to push code to the Solum platform, and receive back the URL (for web apps) of my running application.
I would be able to specify application characteristics, auto scale policies, etc, as inputs while deploying my application. Following is an indicative list of inputs (not intended to be comprehensive) that an application developer can specify while deploying an app to the platform.
| Attribute name | Description | Required? |
|---|---|---|
| App Name | Name of application (Unique at tenant level) | Required |
| Instance Count | Initial number of app instances | Optional (default = 1 instance) |
| Instance Size | Size of each app instance (as determined by RAM, CPU, disk space, allocated to each instance). 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 (default = "small") |
| Artifact | Packaged application code | Required |
| Auto Scale | Should the application auto-scale (Y/N) | Optional (default = N) |
| MinInstances | Minimum number of app instances (lower threshold for the auto scale policy) | Optional (default = 1) |
| MaxInstances | Maximum number of app instances (upper threshold for the auto scale policy) | Optional (default = specified Instance count during app creation) |
| Environment | Set application specific 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 pick 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 a SQL script passed to a database service to create the custom application scheme. | Optional |
