RE: users Digest, Vol 70, Issue 8

[Brigman, Larry]

Fresh installs.  My pods; not the openshift pods.
How do I change the scheduling from false to true for masters as that may solve 
my problem?


-Original Message-
From: Walters, Todd [mailto:todd_walt...@unigroup.com] 
Sent: Friday, May 04, 2018 10:54 AM
To: users@lists.openshift.redhat.com
Subject: Re: users Digest, Vol 70, Issue 8

Hi Larry,

Is it all pods or just the openshift-web-console pods? I’m guessing because, 
when I upgraded from 3.7 to 3.9 I did not realize that the WebUI was now broke 
out into it’s own project and running 1 pod per master. I had to change 
scheduling false to true for my master nodes to allow the web-console pods to 
run on the masters.

todd

Today's Topics:

   2. getting pods running on 3.9 masters (Brigman, Larry)



Message: 2
Date: Fri, 4 May 2018 15:58:13 +
From: "Brigman, Larry" 
To: users 
Subject: getting pods running on 3.9 masters
Message-ID:
<3b94f360ba2c1448b926eadf68c6be1c01f5712...@sdcexmbx2.arrs.arrisi.com>
Content-Type: text/plain; charset="us-ascii"

I can get Openshift 3.9 running with anything that openshift-ansible 
installs.
When I go to run my pods, I always get Pending on the deployment container.
I've tried it with master nodes and with infra nodes in my cluster.
Scheduling Failed 0/3 nodes available

The nodes all report ready.
What is the magic for 3.9.



--

___
users mailing list
users@lists.openshift.redhat.com

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openshift.redhat.com%2Fopenshiftmm%2Flistinfo%2Fusers=01%7C01%7Ctodd_walters%40unigroup.com%7C66dbb6f51c774ff96c2208d5b1d81bf8%7C259bdc2f86d3477b8cb34eee64289142%7C1=5Oqc1B6heLRi1z4UqEyoetnOGGbU6DG58bw7oX5Gi4U%3D=0


End of users Digest, Vol 70, Issue 8





The information contained in this message, and any attachments thereto, is 
intended solely for the use of the addressee(s) and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination, copying, 
or other use of the transmitted information is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer. 
UNIGROUP.COM 



___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: users Digest, Vol 70, Issue 8

[Walters, Todd]

Hi Larry,

Is it all pods or just the openshift-web-console pods? I’m guessing because, 
when I upgraded from 3.7 to 3.9 I did not realize that the WebUI was now broke 
out into it’s own project and running 1 pod per master. I had to change 
scheduling false to true for my master nodes to allow the web-console pods to 
run on the masters.

todd

Today's Topics:

   2. getting pods running on 3.9 masters (Brigman, Larry)



Message: 2
Date: Fri, 4 May 2018 15:58:13 +
From: "Brigman, Larry" 
To: users 
Subject: getting pods running on 3.9 masters
Message-ID:
<3b94f360ba2c1448b926eadf68c6be1c01f5712...@sdcexmbx2.arrs.arrisi.com>
Content-Type: text/plain; charset="us-ascii"

I can get Openshift 3.9 running with anything that openshift-ansible 
installs.
When I go to run my pods, I always get Pending on the deployment container.
I've tried it with master nodes and with infra nodes in my cluster.
Scheduling Failed 0/3 nodes available

The nodes all report ready.
What is the magic for 3.9.



--

___
users mailing list
users@lists.openshift.redhat.com

https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openshift.redhat.com%2Fopenshiftmm%2Flistinfo%2Fusers=01%7C01%7Ctodd_walters%40unigroup.com%7C66dbb6f51c774ff96c2208d5b1d81bf8%7C259bdc2f86d3477b8cb34eee64289142%7C1=5Oqc1B6heLRi1z4UqEyoetnOGGbU6DG58bw7oX5Gi4U%3D=0


End of users Digest, Vol 70, Issue 8





The information contained in this message, and any attachments thereto,
is intended solely for the use of the addressee(s) and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination, copying, or other use of the transmitted information is
prohibited. If you received this in error, please contact the sender
and delete the material from any computer. UNIGROUP.COM



___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Changing ROUTING_SUFFIX?

[Frederic Giloux]

Yes, that's correct. You will need to update old routes. The rational is
that it is a default value not something that is enforced.

Regards,

Frédéric

On Fri, May 4, 2018 at 6:55 PM, Dave Neary  wrote:

> Thanks - that answers my question. It will work on new routes, but not
> old routes - correct?
>
> Thanks,
> Dave.
>
> On 05/04/2018 12:52 PM, Frederic Giloux wrote:
> > Hi Dave,
> >
> > the variable was renamed with 3.2:
> > https://docs.openshift.com/enterprise/3.2/install_config/
> revhistory_install_config.html#thu-may-12-2016
> > after running ansible you can check
> > /etc/origin/master/master-config.yaml you should have these lines with
> > your value:
> > routingConfig:
> >   subdomain: apps.sandbox.com 
> >
> > The master services need to be restarted afterwards:
> > systemctl restart atomic-openshift-master-api
> > systemctl restart atomic-openshift-master-controllers
> > I don't know where it can be checked apart from creating a new route. I
> > gave it a try on my cluster (OCP 3.9 not origin) and it worked right
> > away with an existing project.
> >
> > Regards,
> >
> > Frédéric
> >
> >
> > On Fri, May 4, 2018 at 6:07 PM, Dave Neary  > > wrote:
> >
> > Thanks Frederic,
> >
> > I did this, but the routing suffix still gives the old answer for
> > existing projects - is this expected, or did I do something wrong?
> >
> > Also: I think that in openshift-ansible that the config file is set
> in
> > roles/openshift_facts/defaults/main.yml as 'osm_default_subdomain'
> - is
> > this right?
> >
> > How can I find out what the currently active set value is (just to
> check
> > that the change I made in the config file has been taken into
> > consideration)?
> >
> > Thanks,
> > Dave.
> >
> > On 05/04/2018 12:43 AM, Frederic Giloux wrote:
> > > Hi Dave,
> > >
> > > you can change the suffix at the mater level (you will need to
> restart
> > > the master services):
> > > https://docs.openshift.org/latest/install_config/router/
> default_haproxy_router.html#customizing-the-default-routing-subdomain
> >  default_haproxy_router.html#customizing-the-default-routing-subdomain>
> > > This can be set with ansible by using the variable
> > > openshift_master_default_subdomain in the inventory.
> > > It is also possible to override this setting by specifying the
> hostname
> > > at the route level.
> > >
> > > Regards,
> > >
> > > Frédéric
> > >
> > > On Fri, May 4, 2018 at 12:19 AM, Dave Neary  
> > > >> wrote:
> > >
> > > Hi,
> > >
> > > When I set up OpenShift Origin, I left the default routing
> suffix
> > > .router.default.svc.cluster.local (figured if it needed
> > changing, I'd
> > > find out sooner or later and be able to change it).
> > >
> > > Now I need to change it to have my app work, and I'm unclear
> > what the
> > > best way to do that is - is this a per-project thing, or
> > something that
> > > is set at the OpenShift level? Is it a config file I need to
> > change and
> > > restart Origin, or is this something I dynamically change from
> the
> > > command line?
> > >
> > > I found this page, which talks about changing the option in
> > run-time
> > > with minishift, but I used openshift-ansible, so I'm not sure
> > it I can
> > > do this with oc.
> > >
> >  https://docs.openshift.org/latest/minishift/openshift/
> openshift-client-binary.html
> >  openshift-client-binary.html>
> > >
> >   openshift-client-binary.html
> >  openshift-client-binary.html>>
> > >
> > > Thanks,
> > > Dave.
> > >
> > >
> > > --
> > > Dave Neary - Open Source and Standards team
> > > Red Hat - http://community.redhat.com
> > > Ph: +1-978-399-2182 / Cell: +1-978-799-3338
> > >
> > > ___
> > > users mailing list
> > > users@lists.openshift.redhat.com
> > 
> > >  > >
> > > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> > 
> > >  > >
> > >
> > 

Re: Changing ROUTING_SUFFIX?

[Dave Neary]

Thanks - that answers my question. It will work on new routes, but not
old routes - correct?

Thanks,
Dave.

On 05/04/2018 12:52 PM, Frederic Giloux wrote:
> Hi Dave,
> 
> the variable was renamed with 3.2:
> https://docs.openshift.com/enterprise/3.2/install_config/revhistory_install_config.html#thu-may-12-2016
> after running ansible you can check
> /etc/origin/master/master-config.yaml you should have these lines with
> your value:
> routingConfig:
>   subdomain: apps.sandbox.com 
> 
> The master services need to be restarted afterwards:
> systemctl restart atomic-openshift-master-api
> systemctl restart atomic-openshift-master-controllers
> I don't know where it can be checked apart from creating a new route. I
> gave it a try on my cluster (OCP 3.9 not origin) and it worked right
> away with an existing project.
> 
> Regards,
> 
> Frédéric
> 
> 
> On Fri, May 4, 2018 at 6:07 PM, Dave Neary  > wrote:
> 
> Thanks Frederic,
> 
> I did this, but the routing suffix still gives the old answer for
> existing projects - is this expected, or did I do something wrong?
> 
> Also: I think that in openshift-ansible that the config file is set in
> roles/openshift_facts/defaults/main.yml as 'osm_default_subdomain' - is
> this right?
> 
> How can I find out what the currently active set value is (just to check
> that the change I made in the config file has been taken into
> consideration)?
> 
> Thanks,
> Dave.
> 
> On 05/04/2018 12:43 AM, Frederic Giloux wrote:
> > Hi Dave,
> > 
> > you can change the suffix at the mater level (you will need to restart
> > the master services):
> > 
> https://docs.openshift.org/latest/install_config/router/default_haproxy_router.html#customizing-the-default-routing-subdomain
> 
> 
> > This can be set with ansible by using the variable
> > openshift_master_default_subdomain in the inventory.
> > It is also possible to override this setting by specifying the hostname
> > at the route level.
> > 
> > Regards,
> > 
> > Frédéric
> > 
> > On Fri, May 4, 2018 at 12:19 AM, Dave Neary  
> > >> wrote:
> >
> >     Hi,
> >
> >     When I set up OpenShift Origin, I left the default routing suffix
> >     .router.default.svc.cluster.local (figured if it needed
> changing, I'd
> >     find out sooner or later and be able to change it).
> >
> >     Now I need to change it to have my app work, and I'm unclear
> what the
> >     best way to do that is - is this a per-project thing, or
> something that
> >     is set at the OpenShift level? Is it a config file I need to
> change and
> >     restart Origin, or is this something I dynamically change from the
> >     command line?
> >
> >     I found this page, which talks about changing the option in
> run-time
> >     with minishift, but I used openshift-ansible, so I'm not sure
> it I can
> >     do this with oc.
> >   
>  
> https://docs.openshift.org/latest/minishift/openshift/openshift-client-binary.html
> 
> 
> >   
>  
>  
> >
> >
> >     Thanks,
> >     Dave.
> >
> >
> >     --
> >     Dave Neary - Open Source and Standards team
> >     Red Hat - http://community.redhat.com
> >     Ph: +1-978-399-2182 / Cell: +1-978-799-3338
> >
> >     ___
> >     users mailing list
> >     users@lists.openshift.redhat.com
> 
> >      >
> >     http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> 
> >      >
> >
> >
> >
> >
> > --
> > *Frédéric Giloux*
> > Principal App Dev Consultant
> > Red Hat Germany
> > 
> > fgil...@redhat.com 
> >     M:
> +49-174-172-4661
> > 
> >
> > redhat.com   | TRIED. TESTED.
> TRUSTED. |
> > redhat.com/trusted 

Re: Changing ROUTING_SUFFIX?

[Frederic Giloux]

Hi Dave,

the variable was renamed with 3.2:
https://docs.openshift.com/enterprise/3.2/install_config/revhistory_install_config.html#thu-may-12-2016
after running ansible you can check /etc/origin/master/master-config.yaml
you should have these lines with your value:
routingConfig:
  subdomain: apps.sandbox.com

The master services need to be restarted afterwards:
systemctl restart atomic-openshift-master-api
systemctl restart atomic-openshift-master-controllers
I don't know where it can be checked apart from creating a new route. I
gave it a try on my cluster (OCP 3.9 not origin) and it worked right away
with an existing project.

Regards,

Frédéric


On Fri, May 4, 2018 at 6:07 PM, Dave Neary  wrote:

> Thanks Frederic,
>
> I did this, but the routing suffix still gives the old answer for
> existing projects - is this expected, or did I do something wrong?
>
> Also: I think that in openshift-ansible that the config file is set in
> roles/openshift_facts/defaults/main.yml as 'osm_default_subdomain' - is
> this right?
>
> How can I find out what the currently active set value is (just to check
> that the change I made in the config file has been taken into
> consideration)?
>
> Thanks,
> Dave.
>
> On 05/04/2018 12:43 AM, Frederic Giloux wrote:
> > Hi Dave,
> >
> > you can change the suffix at the mater level (you will need to restart
> > the master services):
> > https://docs.openshift.org/latest/install_config/router/
> default_haproxy_router.html#customizing-the-default-routing-subdomain
> > This can be set with ansible by using the variable
> > openshift_master_default_subdomain in the inventory.
> > It is also possible to override this setting by specifying the hostname
> > at the route level.
> >
> > Regards,
> >
> > Frédéric
> >
> > On Fri, May 4, 2018 at 12:19 AM, Dave Neary  > > wrote:
> >
> > Hi,
> >
> > When I set up OpenShift Origin, I left the default routing suffix
> > .router.default.svc.cluster.local (figured if it needed changing,
> I'd
> > find out sooner or later and be able to change it).
> >
> > Now I need to change it to have my app work, and I'm unclear what the
> > best way to do that is - is this a per-project thing, or something
> that
> > is set at the OpenShift level? Is it a config file I need to change
> and
> > restart Origin, or is this something I dynamically change from the
> > command line?
> >
> > I found this page, which talks about changing the option in run-time
> > with minishift, but I used openshift-ansible, so I'm not sure it I
> can
> > do this with oc.
> > https://docs.openshift.org/latest/minishift/openshift/
> openshift-client-binary.html
> >  openshift-client-binary.html>
> >
> > Thanks,
> > Dave.
> >
> >
> > --
> > Dave Neary - Open Source and Standards team
> > Red Hat - http://community.redhat.com
> > Ph: +1-978-399-2182 / Cell: +1-978-799-3338
> >
> > ___
> > users mailing list
> > users@lists.openshift.redhat.com
> > 
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> > 
> >
> >
> >
> >
> > --
> > *Frédéric Giloux*
> > Principal App Dev Consultant
> > Red Hat Germany
> >
> > fgil...@redhat.com  M: +49-174-172-4661
> > 
> >
> > redhat.com  | TRIED. TESTED. TRUSTED. |
> > redhat.com/trusted 
> > 
> > Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn,
> > Handelsregister: Amtsgericht München, HRB 153243
> > Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham,
> > Michael O'Neill
>
> --
> Dave Neary - Open Source and Standards team
> Red Hat - http://community.redhat.com
> Ph: +1-978-399-2182 / Cell: +1-978-799-3338
>



-- 
*Frédéric Giloux*
Principal App Dev Consultant
Red Hat Germany

fgil...@redhat.com M: +49-174-172-4661

redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn,
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham, Michael
O'Neill
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: getting pods running on 3.9 masters

[Christopher Adigun]

Do you have nodes with the role of COMPUTE?




On Fri, May 4, 2018, 5:58 PM Brigman, Larry  wrote:

> I can get Openshift 3.9 running with anything that openshift-ansible
> installs.
> When I go to run my pods, I always get Pending on the deployment container.
> I've tried it with master nodes and with infra nodes in my cluster.
> Scheduling Failed 0/3 nodes available
>
> The nodes all report ready.
> What is the magic for 3.9.
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Changing ROUTING_SUFFIX?

[Dave Neary]

Thanks Frederic,

I did this, but the routing suffix still gives the old answer for
existing projects - is this expected, or did I do something wrong?

Also: I think that in openshift-ansible that the config file is set in
roles/openshift_facts/defaults/main.yml as 'osm_default_subdomain' - is
this right?

How can I find out what the currently active set value is (just to check
that the change I made in the config file has been taken into
consideration)?

Thanks,
Dave.

On 05/04/2018 12:43 AM, Frederic Giloux wrote:
> Hi Dave,
> 
> you can change the suffix at the mater level (you will need to restart
> the master services):
> https://docs.openshift.org/latest/install_config/router/default_haproxy_router.html#customizing-the-default-routing-subdomain
> This can be set with ansible by using the variable
> openshift_master_default_subdomain in the inventory.
> It is also possible to override this setting by specifying the hostname
> at the route level.
> 
> Regards,
> 
> Frédéric
> 
> On Fri, May 4, 2018 at 12:19 AM, Dave Neary  > wrote:
> 
> Hi,
> 
> When I set up OpenShift Origin, I left the default routing suffix
> .router.default.svc.cluster.local (figured if it needed changing, I'd
> find out sooner or later and be able to change it).
> 
> Now I need to change it to have my app work, and I'm unclear what the
> best way to do that is - is this a per-project thing, or something that
> is set at the OpenShift level? Is it a config file I need to change and
> restart Origin, or is this something I dynamically change from the
> command line?
> 
> I found this page, which talks about changing the option in run-time
> with minishift, but I used openshift-ansible, so I'm not sure it I can
> do this with oc.
> 
> https://docs.openshift.org/latest/minishift/openshift/openshift-client-binary.html
> 
> 
> 
> Thanks,
> Dave.
> 
> 
> -- 
> Dave Neary - Open Source and Standards team
> Red Hat - http://community.redhat.com
> Ph: +1-978-399-2182 / Cell: +1-978-799-3338
> 
> ___
> users mailing list
> users@lists.openshift.redhat.com
> 
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> 
> 
> 
> 
> 
> -- 
> *Frédéric Giloux*
> Principal App Dev Consultant
> Red Hat Germany
> 
> fgil...@redhat.com      M: +49-174-172-4661
> 
> 
> redhat.com  | TRIED. TESTED. TRUSTED. |
> redhat.com/trusted 
> 
> Red Hat GmbH, http://www.de.redhat.com/ Sitz: Grasbrunn,
> Handelsregister: Amtsgericht München, HRB 153243
> Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham,
> Michael O'Neill

-- 
Dave Neary - Open Source and Standards team
Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

getting pods running on 3.9 masters

[Brigman, Larry]

I can get Openshift 3.9 running with anything that openshift-ansible installs.
When I go to run my pods, I always get Pending on the deployment container.
I've tried it with master nodes and with infra nodes in my cluster.
Scheduling Failed 0/3 nodes available

The nodes all report ready.
What is the magic for 3.9.  

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Using RMI Protocol to connect to OpenShift from external application

[Joel Pearson]

Hi Tien,

You just need to create a passthrough route like this:

https://docs.openshift.com/container-platform/3.9/architecture/networking/routes.html#passthrough-termination

For it to work, your swing client needs to use SNI (server name
identification), so that the OpenShift router knows what you're trying to
connect to.  A bit of quick googling suggests that Java 7 supports that,
but it depends if the RMI SSL Client uses SNI or not.

Then you'd need to tell your swing clients to connect to RMI on port 443,
ie :443. This is because that is what port the
router listens on.

Then the router will do the normal things like redirecting the traffic to
your service on whatever port your RMI server is actually running on.

In this passthrough mode, you're essentially using the router as a TCP load
balancer.

I think it has a fair chance of working.

Good luck.

Thanks,

Joel

On Thu, May 3, 2018 at 1:40 AM Tien Hung Nguyen 
wrote:

> Currently, our application is already running on Docker through RMI over
> SSL. Therefore, we are able to connect our client to the server via SSL and
> RMI using Docker.
>
> What do we have to do in order to make it work with OpenShift, now?
>
> 2018-05-02 16:34 GMT+02:00 Joel Pearson :
>
>> Selectors refer to labels, so it’d be
>> deploymentconfig.metadata.labels.name
>>
>> SSL/TLS means the client has to support it too. So if there is some
>> option to run RMI over SSL/TLS then it could work pretty easily. But if
>> it’s not possible to run server and client that way then yes, nodeports
>> will be easier. Otherwise I think there might be other Ingress options. But
>> I’ve never used them.
>> On Thu, 3 May 2018 at 12:14 am, Tien Hung Nguyen <
>> tienhng.ngu...@gmail.com> wrote:
>>
>>> Thank you for the response.
>>>
>>> How can I set up SSL/TLS as a connection method on OpenShift that my
>>> Client connects through SSL/TLS to the server? Is that done on the
>>> OpenShift router or where can I do the settings?
>>>
>>> Otherwise, I think NodePorts are the easier solution to establish a
>>> connection between Client-Server using RMI. In this case, do I just have to
>>> specify the service with the proper NodePort as the property like this
>>> example, where the selector.name is the name of the
>>> deploymentConfig.metadata.name? :
>>>
>>> apiVersion: v1
>>> kind: Service
>>> metadata:
>>>   name: mysql
>>>   labels:
>>> name: mysql
>>> spec:
>>>   type: NodePort
>>>   ports:
>>> - port: 3036
>>>   nodePort: 30036
>>>   name: http
>>>   selector:
>>> name: mysql
>>>
>>>
>>>
>>>
>>>
>>> 2018-05-02 15:53 GMT+02:00 Joel Pearson :
>>>
 If you're using SSL/TLS you could traverse the Router by use
 Passthrough.  Otherwise, you have to use NodePorts on a Service or
 something like that.  The Router is generally only really for HTTP, but
 with passthrough SSL/TLS just about anything could be running in the pod.

 On Wed, May 2, 2018 at 10:52 PM Tien Hung Nguyen <
 tienhng.ngu...@gmail.com> wrote:

> Hi,
>
> we have a application, which is actually running on
> Wildfly 12.0.0.Final via Docker.
> Now, we would like to put our application on OpenShift with the
> existing Dockerfile.
>
> However, our client is using RMI to connect connect to the server. Is
> it still possible to run our application on OpenShift while using RMI for
> the client-server connection? If yes, how should we configure the client
> and the router of OpenShift to connect to the server?
>
> At the moment our java client is using the hostname:port in order to
> connect to the server running on Docker.
>
> Regards,
> Tien
>
> Note: Our application is not a web application, but it is java swing
> application (desktop application) which uses RMI to connect to the server.
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>

>>>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Version settings for installing 3.9

[Tim Dudgeon]

What are the magical set of properties needed to run an ansible install 
of Origin 3.9 on centos nodes?


I've tried various combinations around these but can't get anything to work:

openshift_deployment_type=origin
openshift_release=v3.9
openshift_image_tag=v3.9.0
openshift_pkg_version=-3.9.0

I'm continually getting:

  1. Hosts:    test39-master.openstacklocal
 Play: Determine openshift_version to configure on first master
 Task: openshift_version : fail
 Message:  Package 'origin-3.9*' not found

Surely if you are working from the release-3.9 branch of 
openshift-ansible then you should not need to set any of these versions 
- you should get the latest version of 3.9 images and rpms?


Tim

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users