Given that its a 2960, I'd venture to guess that its tripping up on the
dot1q part, because, if I remember correctly, dot1q is the only supported
encapsulation (no ISL). Is the behavior different if you remove that?
Brandon
On Monday, August 3, 2020 at 6:20:08 PM UTC-7, William Dossett
5:16 UTC, Brandon Daly wrote:
>
> I have a play that is creating yaml for each of my hosts and this is
> stored in './host_vars/{{ inventory_hostname }}/l3vpn.yml
>
> I then have a second play in which I wish to use this yaml.
>
> both are called from another playbook;
>
I have a play that is creating yaml for each of my hosts and this is stored
in './host_vars/{{ inventory_hostname }}/l3vpn.yml
I then have a second play in which I wish to use this yaml.
both are called from another playbook;
[ansible@ansi001 juniper]$ more live.all.pb.yam
---
- import_play
ible.com/ansible/latest/docker_service_module.html
>
> On Mon, Jan 29, 2018 at 2:28 PM, Brandon Schlueter > wrote:
>
>> In writing a playbook to bring up sentry according to its docs with
>> docker-compose, I ended up with a task list including:
>>
>> - name: run d
In writing a playbook to bring up sentry according to its docs with
docker-compose, I ended up with a task list including:
- name: run database migrations
command:
docker-compose run --rm web upgrade --noinput
chdir=/opt/sentry-onpremise
- name: create initial user
command:
docker-compose run --r
rchase a Tower
support contract. Unfortunately, when trying to use these same variables in
surveys, I receive an error that states "Please remove the illegal
character from the survey question variable name". This occurs because AWX
is not interpreting the "." as a valid element.
Hi,
Does documentation exist anywhere on how the various Network modules work
together in 2.3+? I'm looking for something more technical than just how to
use the modules and instead am looking to map out the interdependencies
with all the module_utils and plugins.
Use case:
I use Ansible to
I searched and couldn't find anything saying one way or the other but I am
trying to basically build a bunch of Coreos VMs(just for lab and practice)
using ansible. I can deploy them just fine but I would like to do what I do
in powershell and modify the guestinfo to provide Coreos with its sett
up. Thanks!
On Monday, August 8, 2016 at 7:14:01 PM UTC-7, Brandon Heller wrote:
>
> tl;dr; Seeing an Ansible bug where commands take lots of time to start,
> and then complete quickly; seems to affect Ubuntu VMs.
>
> Full description: I’m using Ansible to orchestrate code deploym
tl;dr; Seeing an Ansible bug where commands take lots of time to start, and
then complete quickly; seems to affect Ubuntu VMs.
Full description: I’m using Ansible to orchestrate code deployments. These
deployments frequently take _much_ longer than expected, because individual
steps that sho
You need one more space in front of your "commands:".
This is correct:
- hosts: 192.168.0.1
gather_facts: False
connection: local
tasks:
- asa_command:
commands:
- sh ver
A YAML parser like http://yaml-online-parser.appspot.com/ is super helpful
in debugging little syn
Has anyone managed to do this? I've been using a lot of the new ansible
network modules but have ran into a snag trying to configure an exec
banner. Looking at accounting logs I see Ansible login, pass the command "
banner exec Z",and then it just does nothing and Ansible times out. I'm
assum
I've found that by copying and modifying ios.py in ../ansible/module_utils/
and then pointing ios_template to this new module its easy to change
"terminal length 0" to "terminal pager 0". Doing so, however, has
apparently broken something else because now Ansible does not interpret
templates co
Greg,
Did you ever find anything out about this? I was asking folks in the IRC
channel about this today. I've been using the Kubernetes and CoreOS slack
groups a lot over the past 6 months, and I've started to really like it. It
would be nice to have a Ansible slack group.
B
--start-at-task seems to be fixed recently.
Thanks, Ansible devs! This is a major improvement to my daily workflow :-)
On Wednesday, December 2, 2015 at 4:10:17 PM UTC-8, Brian Coca wrote:
>
> Currently, this is the price we are paying for the dynamic 'task
> includes', we are looking for ways
Thanks Brian.
Did you have a chance to talk to other devs? Is this a conversation I
could join in?
We've now switched internally to 2.0.0 but I'm finding a lot of debugging
much slower, as I have to use a mix of tags and temporary commenting-out to
get playbooks working.
Thanks,
-b
On Tues
On Nov 30, 2015 11:48 PM, "Brian Coca" wrote:
>
> My tests included a role and a bunch of debug tasks in 2 plays, all
> worked, what did not have is a task include.
>
> This is probably due to the new 'dynamic' nature of tasks includes in
> 2.0, the same reason those tasks don't appear in task lis
ocal
~/src/fwd/ops/ansible/fwd-ubuntu
fwd-ubuntu (testing/alex/docker) 14367 $ ansible-playbook -f 20 -i
inventory/my_host.ini site-simple.yml --list-tasks
playbook: site-simple.yml
play #1 (docker_singlebox): TAGS: []
Test task direct TAGS: []
*Test task TAGS: []*
On Mo
Brian, can you point me to the tests you're running?
As an update to the previous, I gave up on binary searching to find where
the behavior changed; the issue is present at v2.0.0-0.1.alpha1~250 but
before then I see a compilation issue where Ansible thinks quotes are
missing.
On Monday, Nove
osed one, or can you reopen it?
Thanks,
Brandon
On Monday, November 30, 2015 at 5:16:29 PM UTC-8, Brian Coca wrote:
>
> the 'meta' tasks you see there might be the internal calls to `meta:
> refresh_handlers` which don't normally have a name. List tasks in 2.0
&
[prior post had a link in the title - if a mod can delete that post, would
be great, thanks!]
I'm having some issues with ansible 2.0.0-stable (b69942a), where
--start-at-task can't find the task with that name.
I think a clue may be in --list-tasks, which doesn't list task names for
tasks d
Hi,
I'm having some issues with ansible 2.0.0-stable (b69942a), where
--start-at-task can't find the task with that name.
I think a clue may be in --list-tasks, which doesn't list task names for
tasks defined as meta:
[output from --list-tasks]:
PLAY: #5
tasks:
TASK: meta
Has anyone started working on a module for copying files from a file share?
I need to copy files of size greater than 3Mb to a remote system.
I want to ensure I am not duplicating anyone else work.
Thank you,
Brandon Marick
Intel Corporation
--
You received this message because you are
o }
>- { name: app2, base: bar }
>
> tasks:
>- blarg: ...
> with_items: apps
>
> Etc.
>
> Let me know if you'd like more detail on some of the above, but that
> should get you started.
>
>
> On Fri, Jul 18, 2014 at 2:58 PM, Brandon Metcalf <
&g
It seems this should work according to the docs. It does work if I use
with_items: app1
$ cat jj.yml
---
- hosts: all
vars:
app1:
- base: "{{ file | basename }}"
app2:
- base: "{{ file }}"
tasks:
- name: debug
debug: msg="{{ item.base }}"
with_it
I tried something like this in a task, but it didn't work
tags: "{{ 'production' && 'web' }}"
I have a task that uploads some web assets to S3. This is needed for a
"web" tag, but only for "production". In staging, it's unnecessary, so I
have tags like "web,production", and "web,staging" and
I have some roles that always need to be run, whereas, others depend on
tags. I'm specifying tags for my playbook:
ansible-playbook ansible/app.yml --tags='production,web'
My playbook:
roles:
- { role: ruby193, tags: ["web", "queue", "mail"] }
- { role: deployer, tags: ["web", "queue
27 matches
Mail list logo