Difference between revisions of "Solum/FeatureBlueprints/Definitions"
< Solum
Adrian Otto (talk | contribs) |
|||
Line 1: | Line 1: | ||
+ | '''Assembly:''' | ||
+ | A collection of all the <code>Components</code> of an application. Think of this as the running application, and all the stuff it relies on (databases, load balancer setup, etc.). Every Assembly has at least one <code>Component</code>. | ||
+ | |||
+ | '''Component:''' | ||
+ | A part of your application that you want to be able to manage through Solum (start, pause, resume, delete, etc.). These are grouped into an <code>Assembly</code>. | ||
+ | |||
'''Deployment Unit:''' | '''Deployment Unit:''' | ||
− | 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. A deployment unit could be a docker container, an LXC container, a VM, or something else. | + | A deployment unit (DU) is a unit of deployment for the application being deployed into an <code>Assembly</code>. For example, if Solum is configured to use containers for deploying application code, then the a DU would refer to a container instance. A deployment unit could be a docker container, an LXC container, a VM, or something else. |
'''Common actions''' | '''Common actions''' | ||
− | * | + | * Init: registers a new application in Solum and associates it with the user ( no application code is copied; no deployment is performed, yet). |
− | * Deploy | + | * Deploy: deploys the application bits and generates a running application in an <code>Assembly</code>. Associates dependent services as needed. Builds the application bits from code if required. |
+ | * Build: builds the application, but does not create an <code>Assembly</code> to run it in. This is used for build-once-deploy-many use cases. |
Revision as of 19:39, 15 October 2013
Assembly:
A collection of all the Components
of an application. Think of this as the running application, and all the stuff it relies on (databases, load balancer setup, etc.). Every Assembly has at least one Component
.
Component:
A part of your application that you want to be able to manage through Solum (start, pause, resume, delete, etc.). These are grouped into an Assembly
.
Deployment Unit:
A deployment unit (DU) is a unit of deployment for the application being deployed into an Assembly
. For example, if Solum is configured to use containers for deploying application code, then the a DU would refer to a container instance. A deployment unit could be a docker container, an LXC container, a VM, or something else.
Common actions
- Init: registers a new application in Solum and associates it with the user ( no application code is copied; no deployment is performed, yet).
- Deploy: deploys the application bits and generates a running application in an
Assembly
. Associates dependent services as needed. Builds the application bits from code if required. - Build: builds the application, but does not create an
Assembly
to run it in. This is used for build-once-deploy-many use cases.