"Is there any way to deal with autoscaling in a push mode? If I am using
pull mode is only because of the autoscaling..."
Tower has an excellent autoscaling callbacks feature for this.
The node can phone out and say "configure me", and it will reach out and
configure just that node.
It can be en
Yes, different repos sounds good, but yet it might be a bit more work
maintaining the code. Anyway I'll give it a try.
Is there any way to deal with autoscaling in a push mode? If I am using
pull mode is only because of the autoscaling...
Thanks Michael.
El jueves, 20 de febrero de 2014 14:11:
I'd recommend just using push for 99.547% of everyone out there.
You not only get much better logging output, but can do higher levels of
orchestration, and we've got plenty of folks using it in very large
infrastructures.
Alternatively, you can set up different repos for each of your projects an
I am using the groups aproach in some cases, but I can't use it in
pull-mode, can I? The playbook I wrote (with the "when"s) is to be used in
pull-mode.
Thanks Michael.
El miércoles, 19 de febrero de 2014 14:04:38 UTC+1, Michael DeHaan escribió:
>
> "I am using "when"s because I want to have on
"I am using "when"s because I want to have only one playbook and apply the
roles always depending on the machine type. Is there any other way to do
this?"
Yep! Use groups in that one playbook, and have more than one play:
- hosts: common
roles:
- common
- hosts: webservers
roles:
-
Thanks Michael,
I supposed it was that (the when), but yet it seems strange to me the fact
that a handler can be notified and yet skipped.
Anyway, I changed the play and I like it much more.
I just moved all handlers to one separate file and included that file at
the start of the play. Now not o
The other possibility is there is a "creates=" or "removes=" on a handler
that used a command/shell module.
On Tue, Feb 18, 2014 at 7:22 AM, Michael DeHaan wrote:
> Given you have a "when" above, there's a 99.9% chance that's what's
> happening.
>
> If you tag a role with "when", all the ta
Given you have a "when" above, there's a 99.9% chance that's what's
happening.
If you tag a role with "when", all the tasks in it are applied with the
same condition.
None of the tasks would fire, or the handler.
If you want to define a common handler, don't define it with a "when"
condition
I'm having some trouble having a handler executed. It is notified but
skipped. Is there any particular reason why a handler is notified but yet
skipped? I mean, from my point of view, if a handler is notified means
something changed and it needs to be notified and executed no matter what
still
