fabricio 0.5.8

Fabricio, Docker deploy automation tool

Fabricio is a Docker deploy automation tool used along with the Fabric.

Features

• build Docker images

• create containers and services from images with provided tags

• unlimited infrastructures

• Fabric’s parallel execution mode compatibility

• rollback containers or services to previous version

• public and private Docker registries support

• deploy over SSH tunnel (e.g. access to image registry, proxy, etc.)

• migrations apply and rollback

• data backup and restore

• Docker services (Swarm mode)

• Docker stacks (Docker Compose 3.0+)

• Kubernetes configurations

See changelog for detailed info.

Basic example

The most basic fabfile.py you can use with the Fabricio may look something like this:

from fabricio import docker, tasks

app = tasks.DockerTasks(
    service=docker.Container(
        name='app',
        image='nginx:stable-alpine',
        options={
            'publish': '80:80',
        },
    ),
    hosts=['[e-mail]'],
)

Type fab --list in your terminal to see available Fabric commands:

Available commands:

    app.deploy  deploy service (prepare -> push -> backup -> pull -> migrate -> update)

Finally, to deploy such configuration you simply have to execute following bash command:

fab app.deploy

See also Fabricio examples and recipes.

Requirements

Local

• Python 2.7, 3.4*, 3.5*, 3.6*, 3.7*, 3.8*

• (optional) Docker 1.9+ for building Docker images

* Fabric3 is used for compatibility with Python 3.x

Remote

• sshd

• Docker 1.9+

• Docker 1.12+ for using Docker services

Install

pip install fabricio

Note for macOS users

Because of Python 2 on macOS marked as system component you can’t upgrade its modules which are trying to be upgraded during the Fabricio install (e.g. six and setuptools). Instead, you can try to install last version of Python 2 using Homebrew:

brew install python2

and then:

pip2 install fabricio

Contribute

All proposals and improvements are welcomed through a pull request or issue. Just make sure all tests are running fine.

Install test dependencies

pip install .[test]

Running tests

python -m unittest2 discover tests --verbose

Roles and infrastructures

You can define as many roles and infrastructures as you need. The following example shows ‘production’ and ‘test’ configurations for two-roles deploy configuration:

from fabric import colors, api as fab
from fabricio import docker, tasks, infrastructure

@infrastructure
def testing():
    fab.env.roledefs.update(
        api=['[e-mail]'],
        web=['[e-mail]'],
    )

@infrastructure(color=colors.red)
def production():
    fab.env.roledefs.update(
        api=['[e-mail]', '[e-mail]'],
        web=['[e-mail]'],
    )

web = tasks.DockerTasks(
    service=docker.Container(
        name='web',
        image='registry.example.com/web:latest',
        options={
            'publish': ['80:80', '443:443'],
            'volume': '/media:/media',
        },
    ),
    roles=['web'],
)

api = tasks.DockerTasks(
    service=docker.Container(
        name='api',
        image='registry.example.com/api:latest',
        options={
            'publish': '80:80',
        },
    ),
    roles=['api'],
)

Here is the list of available commands:

Available commands:

    production  select production infrastructure, 'production.confirm' skips confirmation dialog
    testing     select testing infrastructure, 'testing.confirm' skips confirmation dialog
    api.deploy  deploy service (prepare -> push -> backup -> pull -> migrate -> update)
    web.deploy  deploy service (prepare -> push -> backup -> pull -> migrate -> update)

‘production’ and ‘testing’ are available infrastructures here. To deploy to a particular infrastructure just provide it before any other Fabric command(s). For example:

fab testing api.deploy web.deploy

See Infrastructures and roles example for more details.

Tags

Almost every Fabricio command takes optional argument ‘tag’ which means Docker image tag to use when deploying container or service. For instance, if you want to deploy specific version of your application you can do it as following:

fab app.deploy:release-42

By default, value for tag is taken from Container/Service Image.

Also it is possible to completely (and partially) replace registry/account/name/tag/digest of image to deploy:

fab app.deploy:registry.example.com/registry-account/app-image:release-42
fab app.deploy:nginx@sha256:36b0181554913b471ae33546a9c19cc80e97f44ce5e7234995e307f14da57268

Rollback

To return container or service to a previous state execute this command:

fab app.rollback

Idempotency

Fabricio always tries to skip unnecessary container/service update. However, update can be forced by adding force=yes parameter:

fab app.deploy:force=yes

Private Docker registry

It is often when production infrastructure has limited access to the Internet or your security policy does not allow using of public Docker image registries. In such case Fabricio offers ability to use private Docker registry which can be used also as an intermediate registry for the selected infrastructure. To use this option you have to have local Docker registry running within your LAN and also Docker client on your PC. If you have Docker installed you can run up Docker registry locally by executing following command:

docker run --name registry --publish 5000:5000 --detach registry:2

When your local Docker registry is up and run you can provide custom registry which will be used as an intermediate Docker registry accessed via reverse SSH tunnel:

from fabricio import docker, tasks

app = tasks.DockerTasks(
    service=docker.Container(
        name='app',
        image='nginx:stable-alpine',
        options={
            'publish': '80:80',
        },
    ),
    registry='localhost:5000',
    ssh_tunnel='5000:5000',
    hosts=['[e-mail]'],
)

See Hello World example for more details.

Building Docker images

Using Fabricio you can also build Docker images from local sources and deploy them to your servers. This example shows how this can be set up:

from fabricio import docker, tasks

app = tasks.ImageBuildDockerTasks(
    service=docker.Container(
        name='app',
        image='registry.example.com/registry-account/app-image:latest-release',
    ),
    hosts=['[e-mail]'],
    build_path='.',
)

By executing command app.deploy Fabricio will try to build image using Dockerfile from the folder provided by build_path parameter. After that image will be pushed to the registry (registry.example.com in the example above). And deploy itself will start on the last step.

See Building Docker images example for more details.

Docker services

Fabricio can deploy Docker services:

from fabricio import docker, tasks

service = tasks.DockerTasks(
    service=docker.Service(
        name='my-service',
        image='nginx:stable',
        options={
            'publish': '8080:80',
            'replicas': 3,
        },
    ),
    hosts=['user@manager'],
)

See Docker services example for more details.

Docker stacks

Docker stacks are also supported (available since Docker 1.13):

from fabricio import docker, tasks

stack = tasks.DockerTasks(
    service=docker.Stack(
        name='my-docker-stack',
        options={
            'compose-file': 'my-docker-compose.yml',
        },
    ),
    hosts=['user@manager'],
)

See Docker stacks example for more details.

Kubernetes configuration

Kubernetes configuration can be deployed using following settings:

from fabricio import kubernetes, tasks

k8s = tasks.DockerTasks(
    service=kubernetes.Configuration(
        name='my-k8s-configuration',
        options={
            'filename': 'configuration.yml',
        },
    ),
    hosts=['user@manager'],
)

See Kubernetes configuration example for more details.