I tried using: ansibleplaybookbundle/origin-ansible-service-broker:latest
but it crashed trying to retrieve cluster roles. So I'm not sure what the
correct option is.
!!filter mode is none[2018-01-05T00:45:57.44Z] [INFO] - Validating
specs...
[2018-01-05T00:45:57.44Z] [NOTICE] - All specs pas
Hi Tim,
Yes, I only discovered what the basion setting did by looking at the heat
template, as I was going to try and remove the need for the bastion by
myself.
I found this line in the heat template:
https://github.com/openshift/openshift-ansible-contrib/blob/master/roles/openstack-stack/templat
Ahh Thanks, I wondered if there would be a side effect.
I discovered that the directory we're using, OpenDJ, has virtual
attributes, and one of those attributes is "isMemberOf", so I was able to
use:
url: ldap://
ldap.company.com.au:1389/ou=people,dc=company,dc=com,dc=au?uid?sub?(isMemberOf=cn=st
Joel,
Thanks for that.
I had seen this but didn't really understand what it meant.
Having read through it again I still don't!
I'll give it a try tomorrow and see what happens.
As for the warning about scaling up/down then yes, that is a big
concern. That's the whole point of getting automation
I'm trying to install origin 3.7 on centos 7 running on AWS via the
advanced install. When I run ansible I get the following:
TASK [openshift_cloud_provider : Configure AWS cloud provider]
***
fatal: [10.0.4.160]: FAILED! => {"failed": true, "msg": "The task includes
I had exactly the same concern and I discovered that inside the heat
template there is a bastion mode, which once enabled it doesn’t use
floating ip’s any more.
Have a look at
https://github.com/openshift/openshift-ansible-contrib/blob/master/playbooks/provisioning/openstack/advanced-configuration
I hope this is the right place to ask questions about the
openshift/openshift-ansible-contrib GitHub repo, and specifically the
playbooks for installing OpenShift on OpenStack:
https://github.com/openshift/openshift-ansible-contrib/tree/master/playbooks/provisioning/openstack
If not then please
I'm hitting a number of issues with installing logging and metrics on
Origin 3.7.
This is using Centos7 hosts, the release-3.7 branch of openshift-ansible
and NFS for persistent storage.
I first do a minimal deploy with logging and metrics turned off.
This goes fine. On the NFS server I see var
On Thu, Jan 4, 2018 at 5:35 AM, Joel Pearson
wrote:
> Hi,
>
> I just wanted to check what the proper way is to limit which users are
> allowed to login to OpenShift via an LDAP group.
>
> There doesn't seem to be a way during authentication, but on the
> authorisation side of things I found that
Thanks for your guidance so far Maciej but none of this is working for me. [1]
doesn’t really help as I’m past that and, sadly the 1,500 lines and numerous of
posts in issue 9584 [2] are exhausting to trawl though and still leave me with
an inability to pull from GitLab using an image stream.
A
Hi,
I just wanted to check what the proper way is to limit which users are
allowed to login to OpenShift via an LDAP group.
There doesn't seem to be a way during authentication, but on the
authorisation side of things I found that if I removed
"system:authenticated" from the basic-user cluster ro
Hi,
I've installed OpenShift 3.7.0 containerized on OpenStack, and I'm getting
some issues with the service catalog. It's spewing heaps of errors into
the journal. Lots of very large errors.
In the end it looks like it isn't deploying properly because it can't find
the tag it is after, as I foun
12 matches
Mail list logo