Yeah, I think I'd need to create symlinks to all the group_vars too.
Actually, I'm not too sure how it could work because each inventory file
looks like this:
[web]
somehost
[web]
some_other_host
On Monday, 4 September 2017 14:00:34 UTC+1, J Hawkesworth wrote:
>
> You could just keep your indi
They are at the moment at least webservers each hosting a project or group of
projects relating to a particular client. It makes resource allocation and
billing easier. It affords us the facility to throw hardware resources or scale
up a client's needs. But although each server is essentially a
I could duplicate the hosts in each project in to one central hosts file (yuk)
and at least that way I could run an ad hoc command and target them. I couldn't
rely on group_vars or host_vars though - I'd have to pass in parameters in a
playbook directly or on the command line I guess.
--
You r
So after converting my structure to the "each project has its own ansible.cfg
and inventory" the worst issue I don't appear to be able to solve is targeting
hosts in different projects. If I need to run an ad hoc command on all hosts, I
literally have to enter each project directory and run the
I just tried the alternative approach that I was thinking about and this is
working however two problems
- A lot of configuration repetition between projects that are different but
similar. I guess it's a balance between finding configuration in multiple
places and less repetition vs. one confi
Hey
I'm really struggling to find a solution or "best practise" that enables me
to use Ansible to manage multiple different projects, while still being
able to reuse roles between them to target hosts from all projects in a
play.
Every tutorial or document I read seems to assume you are provis
