This week we have Greg, Mike, and the dread pirate Nick A. Ready, set, chat.
**Sponsors**
Sonar.software
Kwikbit.com
Towercoverage.com
**/Sponsors**
This week we talk about:
MTK chateau
MTK KNOT
MTK switches CRxxx line, be sure to have hardware “on” your kit to ensure maximum throughput.
The snowpocalypse was fun in Texas.
Grande lost most fiber service in Texas for about 12 hours.
Migrating Ansible Tower from centos 7 to RHEL 8…”let’s learn everything really fast shall we”
Networking foundations CLI
Demo2win! training for technical demonstrations
Here’s the video:(if you don’t see it, hit refresh)
This week we have Greg, Mike, and the dread pirate Nick A. Ready, set, chat.
**Sponsors**
Sonar.software
Kwikbit.com
Towercoverage.com
**/Sponsors**
This week we talk about:
MTK chateau
MTK KNOT
MTK switches CRxxx line, be sure to have hardware “on” your kit to ensure maximum throughput.
The snowpocalypse was fun in Texas.
Grande lost most fiber service in Texas for about 12 hours.
Migrating Ansible Tower from centos 7 to RHEL 8…”let’s learn everything really fast shall we”
Networking foundations CLI
Demo2win! training for technical demonstrations
Here’s the video:(if you don’t see it, hit refresh)
I was recently leading an Ansible workshop when someone asked me if you could accept input from a survey in an ansible and use that as a list in a playbook. I worked out a quick solution that I figure may be useful for others too.
I first created a quick survey that would pass a text area to a playbook.
As you can see it passes the survey info over to the playbook as “test_data”. It’s important to remember that the list entries should be one per line.
Next I threw together a quick playbook that will accept the collected info(survey-list.yml):
1 2 3 4 5 6 7 8 9 10 11 12 13 14 | ---
- name: test message area
hosts: localhost
gather_facts: false
vars:
tasks:
- name: debug stuff
debug:
var: test_data
- name: run it as a list
debug:
msg: "{{ item }}"
loop: "{{ test_data.split('\n') }}" |
Taking a look at the playbook tasks I’m doing two things.
In the first task I’m using the debug module to just dump the contents of the test_data variable.
In the second task I’m looping through the data and spitting out the results one at a time. Notice that I’m taking the same variable and using the split option to break them up into separate entries based on the new line character ‘\n’.
Here’s the output of the run:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | PLAY [test message area] *******************************************************
TASK [debug stuff] *************************************************************
ok: [localhost] => {
"test_data": "one\ntwo\nthree\nfour"
}
TASK [run it as a list] ********************************************************
ok: [localhost] => (item=one) => {
"msg": "one"
}
ok: [localhost] => (item=two) => {
"msg": "two"
}
ok: [localhost] => (item=three) => {
"msg": "three"
}
ok: [localhost] => (item=four) => {
"msg": "four"
}
PLAY RECAP *********************************************************************
localhost : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 |
Notice in the debug stuff task it has all the entries with the “\n” new lines jammed in between them.
The second task shows the output listed in four separate entries.
So now I can successfully iterate over anything provided by the survey text area!
Thanks and happy automating.
This week we have Greg and Mike…we are two strong, independent people and don’t need nobody else.
**Sponsors**
Sonar.software
Kwikbit.com
Towercoverage.com
**/Sponsors**
This week we talk about:
Arizona Sunshine multiplayer is all kinds of fun
We had a chat with Simon Westlake from Sonar
Some Netonix switches will power down if there’s no load present on them…
Mikrotik V6.49beta11 – LOTs of fixes: crs3xx packet duplication bonding, pwr-line interface linking, switch fixed interface toggling
Mikrotik commands via automation that require interaction…use the execute command
Customer web interface to reboot PoE ports
Modsec
fail2ban
Speedtest introduces video test – IOS users only for now
Leaky feeder cable
UA-Hotel hotel locks hit the FCC 13MHz and bluetooth
AF60-HD
Ubiquiti Talk Conference
Starlink RIPE Atlas
Here’s the video:(if you don’t see it, hit refresh)
This week we have Greg and Mike…we are two strong, independent people and don’t need nobody else.
**Sponsors**
Sonar.software
Kwikbit.com
Towercoverage.com
**/Sponsors**
This week we talk about:
Arizona Sunshine multiplayer is all kinds of fun
We had a chat with Simon Westlake from Sonar
Some Netonix switches will power down if there’s no load present on them…
Mikrotik V6.49beta11 – LOTs of fixes: crs3xx packet duplication bonding, pwr-line interface linking, switch fixed interface toggling
Mikrotik commands via automation that require interaction…use the execute command
Customer web interface to reboot PoE ports
Modsec
fail2ban
Speedtest introduces video test – IOS users only for now
Leaky feeder cable
UA-Hotel hotel locks hit the FCC 13MHz and bluetooth
AF60-HD
Ubiquiti Talk Conference
Starlink RIPE Atlas
Here’s the video:(if you don’t see it, hit refresh)
This special cast has Greg, Mike, Chad Wachs, and Simon Westlake talking about where Sonar is and where they are going. I believe we have some choppy video on this one, so sorry about that. I also think this is session one with a follow up in the future. Please let us know if you have any questions for the next go around.
This week we talk about:
This cast we talk about:
Building for flexibility
Special “casts” giving info(possibly more in the future)
Why they push for calling support
Ideal customer
V2 roadmaps
Feature parity between V1 and V2
What excites Simon right now
Magma LTE Core
Working with Facebook/Microsoft
Twillio integration for text messaging
Graphql API
Here’s the video:(if you don’t see it, hit refresh)
This special cast has Greg, Mike, Chad Wachs, and Simon Westlake talking about where Sonar is and where they are going. I believe we have some choppy video on this one, so sorry about that. I also think this is session one with a follow up in the future. Please let us know if you have any questions for the next go around.
This week we talk about:
This cast we talk about:
Building for flexibility
Special “casts” giving info(possibly more in the future)
Why they push for calling support
Ideal customer
V2 roadmaps
Feature parity between V1 and V2
What excites Simon right now
Magma LTE Core
Working with Facebook/Microsoft
Twillio integration for text messaging
Graphql API
Here’s the video:(if you don’t see it, hit refresh)