Skip to content
This repository has been archived by the owner on Jan 19, 2018. It is now read-only.

Adds Atomicapp lifecycle definition. Closes #290 #560

Merged
merged 1 commit into from
Feb 16, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions docs/atomicapp_lifecycle.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
Atomicapp Lifecycle Definition
==============================

The Atomic App software allows for several actions to be applied to
specified applications. The four actions that exist today are briefly
described below.

`genanswers`
------------
Will download and combine artifacts from the target application in a
temporary directory and then take the generated sample answers.conf
file and populate it in the users working directory. The temporary
directory is then cleaned up.

`fetch`
-------
Will download and combine artifacts from the target application and any
dependent applications including sample answers.conf file into a local
directory for inspection and/or modification. Same for all providers.

`run`
-----
Run an application.

| Provider | Implementation |
| ------------- | -------------- |
| Docker | Run application containers on local machine. |
| Kubernetes | Run requested application in kubernetes target environment. |
| Openshift | Run requested application in OpenShift target environment. |
| Marathon | Run requested application in Marathon target environment. |

`stop`
------
Stop an application.

| Provider | Implementation |
| ------------- | -------------- |
| Docker | Stop application containers on local machine. |
| Kubernetes | Stop requested application in kubernetes target environment. |
| Openshift | Stop requested application in OpenShift target environment. |
| Marathon | Stop requested application in Marathon target environment. |