OpenShift plans

2017-07-03 Thread Paul W. Frields
So we currently have a staging instance of OpenShift Container Platform -- what are the next actions needed to get a production deployment going? (My understanding is that, as a new service, we're not blocked by infra freeze itself, but there may be other things in the way on top of just having cy

Re: OpenShift plans

2017-07-03 Thread Pierre-Yves Chibon
On Mon, Jul 03, 2017 at 01:12:48PM -0400, Paul W. Frields wrote: > So we currently have a staging instance of OpenShift Container > Platform -- what are the next actions needed to get a production > deployment going? My understanding is that we are at least waiting on the wildcard cert for it. P

Re: OpenShift plans

2017-07-03 Thread Kevin Fenzi
On 07/03/2017 11:17 AM, Pierre-Yves Chibon wrote: > On Mon, Jul 03, 2017 at 01:12:48PM -0400, Paul W. Frields wrote: >> So we currently have a staging instance of OpenShift Container >> Platform -- what are the next actions needed to get a production >> deployment going? > > My understanding is th

Re: OpenShift plans

2017-07-03 Thread Pierre-Yves Chibon
On Mon, Jul 03, 2017 at 11:51:03AM -0600, Kevin Fenzi wrote: > On 07/03/2017 11:17 AM, Pierre-Yves Chibon wrote: > > On Mon, Jul 03, 2017 at 01:12:48PM -0400, Paul W. Frields wrote: > >> So we currently have a staging instance of OpenShift Container > >> Platform -- what are the next actions needed

Re: OpenShift plans

2017-07-03 Thread Jeremy Cline
On 07/03/2017 01:51 PM, Kevin Fenzi wrote:> The next steps are: > > * Make sure our plan for managing apps/routers/etc will work. Basically > we thought we would check in .json configs in ansible and then have it > run os commands loading those. We need a app using that method to > confirm it work

Re: OpenShift plans

2017-07-04 Thread Brian Exelbierd
On Mon, Jul 3, 2017, at 11:05 PM, Jeremy Cline wrote: > On 07/03/2017 01:51 PM, Kevin Fenzi wrote:> The next steps are: > > > > * Make sure our plan for managing apps/routers/etc will work. Basically > > we thought we would check in .json configs in ansible and then have it > > run os commands l

Re: OpenShift plans

2017-07-04 Thread Kevin Fenzi
On 07/03/2017 03:05 PM, Jeremy Cline wrote: > On 07/03/2017 01:51 PM, Kevin Fenzi wrote:> The next steps are: >> >> * Make sure our plan for managing apps/routers/etc will work. Basically >> we thought we would check in .json configs in ansible and then have it >> run os commands loading those. We

Re: OpenShift plans

2017-07-04 Thread Kevin Fenzi
On 07/04/2017 04:22 AM, Brian Exelbierd wrote: > > > On Mon, Jul 3, 2017, at 11:05 PM, Jeremy Cline wrote: >> On 07/03/2017 01:51 PM, Kevin Fenzi wrote:> The next steps are: >>> >>> * Make sure our plan for managing apps/routers/etc will work. Basically >>> we thought we would check in .json conf

Re: OpenShift plans

2017-07-04 Thread Brian Exelbierd
On Tue, Jul 4, 2017, at 07:17 PM, Kevin Fenzi wrote: > On 07/04/2017 04:22 AM, Brian Exelbierd wrote: > > > > > > On Mon, Jul 3, 2017, at 11:05 PM, Jeremy Cline wrote: > >> On 07/03/2017 01:51 PM, Kevin Fenzi wrote:> The next steps are: > >>> > >>> * Make sure our plan for managing apps/routers/

Re: OpenShift plans

2017-07-05 Thread Randy Barlow
On Tue, 2017-07-04 at 11:16 -0600, Kevin Fenzi wrote: > I am pretty sure you can get it to dump out the json > of the existing config, so you could in theory set things up, adjust > via > the web interface and get it the way you want it, then dump the json > and > we can use that in prod. I think

Re: OpenShift plans

2017-07-05 Thread Dan Callaghan
Excerpts from Randy Barlow's message of 2017-07-05 13:42 -04:00: > On Tue, 2017-07-04 at 11:16 -0600, Kevin Fenzi wrote: > > I am pretty sure you can get it to dump out the json > > of the existing config, so you could in theory set things up, adjust > > via > > the web interface and get it the way

Re: OpenShift plans

2017-07-05 Thread Dan Callaghan
Excerpts from Dan Callaghan's message of 2017-07-06 09:05 +10:00: > Here is an example below (and btw I suggest YAML over JSON because > it's easier to edit, oc happily deals in either format). You can see > large parts are not configuration, for example the top-level "status" > key, "creationTi

Re: OpenShift plans

2017-07-17 Thread Paul W. Frields
On Mon, Jul 03, 2017 at 08:01:16PM +0200, Pierre-Yves Chibon wrote: > On Mon, Jul 03, 2017 at 11:51:03AM -0600, Kevin Fenzi wrote: > > On 07/03/2017 11:17 AM, Pierre-Yves Chibon wrote: > > > On Mon, Jul 03, 2017 at 01:12:48PM -0400, Paul W. Frields wrote: > > >> So we currently have a staging insta

Re: OpenShift plans

2017-07-17 Thread Stephen John Smoogen
On 17 July 2017 at 12:23, Paul W. Frields wrote: > On Mon, Jul 03, 2017 at 08:01:16PM +0200, Pierre-Yves Chibon wrote: >> On Mon, Jul 03, 2017 at 11:51:03AM -0600, Kevin Fenzi wrote: >> > On 07/03/2017 11:17 AM, Pierre-Yves Chibon wrote: >> > > On Mon, Jul 03, 2017 at 01:12:48PM -0400, Paul W. Fri

Re: OpenShift plans

2017-07-19 Thread Stephen John Smoogen
On 17 July 2017 at 12:26, Stephen John Smoogen wrote: > On 17 July 2017 at 12:23, Paul W. Frields wrote: >> On Mon, Jul 03, 2017 at 08:01:16PM +0200, Pierre-Yves Chibon wrote: >>> On Mon, Jul 03, 2017 at 11:51:03AM -0600, Kevin Fenzi wrote: >>> > On 07/03/2017 11:17 AM, Pierre-Yves Chibon wrote: