[debops] Philosophical design usage of debops

Hendrik Visage hvjunk at gmail.com
Mon Sep 7 04:37:36 CEST 2015


On Sun, Sep 6, 2015 at 12:27 AM, Maciej Delmanowski <drybjed at drybjed.net> wrote:

>> Sorry to ask the newbie questions <blush>
>
> No problem. I realize that the project documentation is still lacking,
> especiially the first steps, and I try to bring myself to update it, but it's
> hard for me to know what to write about from the beginner perspective,

Examples/Guides/How-tos for making own playbooks etc.
(Not trying to be critical, but just explaining my "fun" today :) )

examples of playbooks that will "run". ie.

I have this playbook:
<code>
#The file used to bootstrap anything specific that we'll need
---

- hosts: all
  sudo: yes
  roles:
    - role: bootstrap-hv
    - role: debops.docker
      tags: [ 'role::docker' ]
</code>

running with: "debops bootstrap -l dev-hv2 --ask-sudo-pass"

Even though I have "ferm: False" in a file in the file
$PROJECT/ansible/inventory/group_vars/all/dockers, it fails with:


TASK: [debops.ferm | Install ferm configuration directories] ******************
ok: [usc-dev-hv2]

TASK: [debops.ferm | Patch ferm init script] **********************************
failed: [usc-dev-hv2] => {"failed": true}
msg: The text leading up to this was:
--------------------------
|--- ferm 2015-09-04 12:02:07.843105402 +0200
|+++ ferm 2015-09-04 11:58:25.159110930 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored


FATAL: all hosts have already failed -- aborting




More information about the debops-users mailing list