1 # Distribution of OSM SW as Docker container images #
13 OSM SW distribution is currently done as source code, which is downloaded by an
14 installer, which also creates several LXD containers for each component, and
15 builds the SW on those containers.
17 Docker containers provide an appropriate framework to separate the different
18 processes of a system in individual process containers so that the system
19 becomes much more flexible in field (for instance, HA or scale-out strategies
20 for an OSM system might be quickly aligned with the state of the art). With the
21 Docker approach, you get freedom to deploy each process in a different place,
22 scale them independently, design your own approach for High Availability, etc.
24 This feature proposes the separation of the different OSM processes in Docker
25 container images. Here the use of the term ''process'' instead of ''component''
26 is intentional. '''Processes running on each component must be identified and
27 Docker containers must be created per process and not per component'''.
29 ## Demo or definition of done ##