Le 25/01/2021 à 16:03, John Petro a écrit :
Good morning,
I am working on setting up an ansible repository, for work. We are
going to be using AWX eventually ( sooner rather than later ). What I
am wondering, is how people decided to split up their ansible project
directories. My first
On Monday 25 January 2021 at 20:37:31, Aris Aguirre wrote:
> you cant...cos a lot of characters there.. i cant find a way how to delete
> them in regex.
Can you explain to us exactly what you want the command to identify?
Are there, for example, certain characters which should never appear in a
you cant...cos a lot of characters there.. i cant find a way how to delete
them in regex.
On Monday, January 25, 2021 at 1:05:37 PM UTC-6 raub...@gmail.com wrote:
> On Mon, Jan 25, 2021 at 1:58 PM Aris Aguirre wrote:
> >
> > I can easily use a file module to delete the existing file and create
On Mon, Jan 25, 2021 at 1:58 PM Aris Aguirre wrote:
>
> I can easily use a file module to delete the existing file and create a new
> one with File1 content.
> But I want to modifile the file using lineinfile or replace. Please help.
> Thanks
>
> Existing File:
> This is an existing file / $ % wi
I can easily use a file module to delete the existing file and create a new
one with File1 content.
But I want to modifile the file using lineinfile or replace. Please help.
Thanks
Existing File:
This is an existing file / $ % with invalid characters &*() Blahh
Expected Output:
File1
--
You re
I was thinking of Block Rescue Always here. Thank you for your input.
On Monday, January 25, 2021 at 11:14:47 AM UTC-6 jruar...@gmail.com wrote:
> - hosts: localhost
> become: True
> gather_facts: False
> vars:
> disk: loop0
> vg_name: vgname
> lv_name: lvname
> default_lv_size: 400M
> tasks:
> -
No it doesn't. It works as you want.
(ansible-2.9.15) dick.visser@mbp ~$ ansible-playbook
work/tasks/list3.yml -e env=DEV
[WARNING]: No inventory was parsed, only implicit localhost is available
PLAY [localhost] ***
TASK [fail] ***
- hosts: localhost
become: True
gather_facts: False
vars:
disk: loop0
vg_name: vgname
lv_name: lvname
default_lv_size: 400M
tasks:
- name: Collect hardware facts
setup:
gather_subset:
- hardware
- name: Register {{ disk }} size
set_fact:
secondary_disk_size: "{{
hostvars[inventory_hostname].ansibl
You have env: Acceptance in there but if you had it DEV or UAT or PROD,
it would have worked. I mean If you use DEV or UAT or PROD as value of
env, then it's all good which is fine. The problem is when the value of env
is just D (first letter of DEV) ie env: D, it still matches DEV.
On Mon,
hmmm,, where to add the message? message to needs to show up like "hosts
has 30G only creating 20G" before creating the 20G lvm?
Thank you
On Monday, January 25, 2021 at 9:37:49 AM UTC-6 jruar...@gmail.com wrote:
> Something like this would do the trick:
>
> In this case I'm using loop0 instead
Something like this would do the trick:
In this case I'm using loop0 instead of sdb.
If loop0 size is higher than 2 GB (assuming no conversion to MB, that would
be great too).
It will set lv_size var to 500M, and thar value will be used in lvol task
otherwise it will use default lv size which is 4
On Mon, 25 Jan 2021 at 14:54, PluftPlayzRoblox wrote:
>
> Trying this:
>
> vars:
> environments: ['DEV Managed, UAT in the datacenter, PROD (in the cloud
> and data center)’]
As I've explained this is incorrect and does not mean what you think it means.
>env: NA
>
> tasks:
> - fail: ms
We do not maintain an independent docker image for ansible itself.
You should look into the ansible-runner image, as that is the base used by
ansible-builder, and will become more common with the introduction of
execution environments.
On Sun, Jan 24, 2021 at 10:45 AM dakotah...@gmail.com <
dakot
Good morning,
I am working on setting up an ansible repository, for work. We are
going to be using AWX eventually ( sooner rather than later ). What I am
wondering, is how people decided to split up their ansible project
directories. My first thought was to just have a single project with all
On 1/25/21 3:34 PM, Rene Paquin wrote:
> Thanks for the response but I do have pexpect3 installed on both the ansible
> server as well as the server I am managing.
>
>
>
> Rene
The question is if you installed pexpect into your Python3 instance. If you
have also a Python2 instance on the ta
Can you please show me how to do that? will this show an error? before
creating the LVM?
On Monday, January 25, 2021 at 8:38:24 AM UTC-6 jruar...@gmail.com wrote:
> You can fetch secondary disk size and set the lvm size depending on it.
> This is what I would do in your case:
>
>- Set defau
You can fetch secondary disk size and set the lvm size depending on it.
This is what I would do in your case:
- Set default lvm size to a safe value that you know all your hosts will
meet. ie : 20G
- Fetch secondary disk size. If it's 50G or higher overwrite default lvm
size to 40G
Re
Thanks for the response but I do have pexpect3 installed on both the ansible
server as well as the server I am managing.
Rene
From: ansible-project@googlegroups.com On
Behalf Of Dick Visser
Sent: January 23, 2021 1:25 AM
To: ansible-project@googlegroups.com
Subject: Re: [ansible-project] Pytho
I have hosts that has 50G and 30G of SDB or disk2..
My playbook only works if hosts has SDB is 50G, then it has no problem
creating the 40G.
But it throwing errros because some hosts has 30G of SDB.
I want my playbook to still run, if the SB has only 30G then it will say,
not enough disk, the
On Monday 25 January 2021 at 15:15:56, ursa Brown wrote:
> I got 2 hosts,
> one has 50G and the other one has 30G.
> I have no problem creating a 40G LVM on the hosts that has 50G. But how can
> I make my ansible script if the hosts has 30G. It will say not enough space
> then create 20G of lvm in
I got 2 hosts,
one has 50G and the other one has 30G.
I have no problem creating a 40G LVM on the hosts that has 50G. But how can
I make my ansible script if the hosts has 30G. It will say not enough space
then create 20G of lvm instead.
Thanks
--
You received this message because you are subs
Trying this:
vars:
environments: ['DEV Managed, UAT in the datacenter, PROD (in the cloud
and data center)’]
env: NA
tasks:
- fail: msg="Not valid value"
when: env |upper not in environments |upper
and with the yaml list, esult is the same, NA matched Managed.
What I found is that if
Thank you!
I wonder why i didn't try it...
On Sun, Jan 24, 2021 at 9:28 PM jbor...@gmail.com
wrote:
> Just loop the services entry and then your item is item.name.
>
> - win_service:
> name: '{{ item.name }}'
> state: started
> with_items: '{{ service.services }}'
>
> This works becaus
23 matches
Mail list logo
