Good idea Joel.
In the inventory file I can use
'bindPassword': '{{ ldap_bind_password }}'
and pass *-e ldap_bind_password=x* when running the playbook.
Ansible vault is probably the way to go but this will do for now.
Thanks!
On 24 October 2017 at 17:19, Joel Pearson
I'm having difficulty with dns resolution when using the ansible
installer in an openstack environment.
Part of the problem is that openstack does not seem able to resolve
hostnames on the local subnet and so some tricks/hacks are needed (this
is not an openshift issue but if anyone knows how
Hi :)
You can , you can deploy additional router and setup the domain that it
will be operating. We did similar approach, we have got internal
applications, and external ones (internet access and exposure into the
internet). You can assigne route to particualr namespace (project) and
operate
HI,
we're discovering an installation of Openshift Origin 3.6 with some app
nodes present on a VLAN (development) and some other app nodes on a public
VLAN (UAT) and we would use the labels and node selector to deploy the pods
for the 2 different projects on their specified nodes. The problem is
Maybe if you use a vars yaml file, it might work? I was going to try it
today, but I didn't get around to it, was hoping you'd get it working first?
By a vars file I mean
ansible-playbook -e "@varsfile.yml"
With something like this in there, but obviously the encrypted bit
