Great! This would make an awesome role.
-- Michael
> On Dec 27, 2013, at 3:16 PM, PePe Amengual wrote:
>
> I'm doing exactly this and once I finish I will uploaded it to Ansible
> galaxy.
>
> The rolling restart and LB pool problem is very easy to solve if you have a
> LB that could check
I'm doing exactly this and once I finish I will uploaded it to Ansible
galaxy.
The rolling restart and LB pool problem is very easy to solve if you have a LB
that could check a status file to be present on the webserver and if not
present take that server out of the pool automatically then
That's a pretty neat trick!
BTW, rather than using the "ls" command, I'd recommend using the "stat"
module for that purpose, since it's a little more explicit and dedicated to
the task.
http://ansibleworks.com/docs/modules.html#stat
run with "-v" to see all the data that it returns.
On Thu,
Yep, exactly.
I would probably do something like making the path the git module include
the version number in the destination path {{ version }}
and that way you wouldn't have to do a live update on the code existing
code tree.
(General disclaimer -- Many folks would use a load balancer instead
Doesn't matter as it is for playbooks.
-- Michael
On Dec 27, 2013, at 1:35 PM, TextEditor wrote:
Seems logical. Can you maybe explain why it worked in 1.3 on task files?
Op vrijdag 27 december 2013 15:21:58 UTC+1 schreef Michael DeHaan:
>
> This command is only intended for running on the top
And that one does work with 1.4:
ansible-playbook --syntax-check --list-tasks -i tests/ansible_hosts
./playbooks/default-vps-setup.yml
[...]
ERROR: Syntax Error while loading YAML script,
/home/remy/ansible/playbooks/roles/vim/tasks/main.yml
Note: The error may actually appear before this posi
Seems logical. Can you maybe explain why it worked in 1.3 on task files?
Op vrijdag 27 december 2013 15:21:58 UTC+1 schreef Michael DeHaan:
>
> This command is only intended for running on the top level playbook. It
> is not intended for running directly on task files which are by definition
>
no but easy to implement with ansible:
- action: whatever you need to deploy code to release specific dir
(git/copy/unarchive/etc)
- file: path=/procuduction/link src=/path/you/just/deployed/to
- service: name=appserver state=reloaded|restarted
--
You received this message because you are subs
I was suggesting this be posed on ansible-devel list btw, will let you post
there and we can discuss.
-- Michael
On Dec 27, 2013, at 7:15 AM, "herby.gil...@axial.net" <
herby.gil...@axial.net> wrote:
RE: https://github.com/ansible/ansible/pull/5430
The intent here was to make it possible for us
This command is only intended for running on the top level playbook. It is
not intended for running directly on task files which are by definition not
playbooks.
-- Michael
On Dec 27, 2013, at 2:16 AM, TextEditor wrote:
It is run on the YAML files because when run on just the playbook which
in
Sorry, I forgot to mention, when looking through the code, I realized in order
to get it to check all the roles too, you need to use the --list-tasks argument
too:
ansible-playbook --syntax-check --list-tasks site.yml
--
Matt Martz
m...@sivel.net
On December 27, 2013 at 8:05:50 AM, TextEditor
Even when a broken playbook or a broken yaml file is includes as role it
validates as correct with 1.4.
Op vrijdag 27 december 2013 08:16:26 UTC+1 schreef TextEditor:
>
> It is run on the YAML files because when run on just the playbook which
> includes the roles it does not check the includes r
Hi Rella.
Please test this code.
Reboot is background process.
So, not pending.
- name: reboot
shell: sleep 2s && /sbin/reboot &
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails fro
RE: https://github.com/ansible/ansible/pull/5430
The intent here was to make it possible for users of the ec2 inventory
module to be able to directly address hosts using groups in the format of
'='
The patch does not change existing behavior, and keeps the legacy format of
host groups for tags
Hello,
I was wondering if anyone was aware of a playbook or module out in the wild
that handled atomic deployments similar to the copy strategy in Capistrano 2?
Thanks in advance,
Stan
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsu
15 matches
Mail list logo
