[Container-tools] docker container based installers for Atomic / OpenShift V3 / GKE et al (was Re: Container App Spec and Tooling

[Clayton Coleman]

> On May 1, 2015, at 4:46 AM, Jimmi Dyson <jdyson at redhat.com> wrote:
> 
> ----- Original Message -----
>> 
>>> On 1 May 2015, at 09:36, Jimmi Dyson <jdyson at redhat.com> wrote:
>>> 
>>> 
>>> 
>>> ----- Original Message -----
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA256
>>>> 
>>>> You are right, good idea!! //G
>>>> 
>>>> On 04/30/2015 04:17 PM, James Strachan wrote:
>>>>>>> TBH I’m currently leaning towards using OpenShift Templates
>>>>>>> everywhere; so there’s only 1 provider;
>>>>>> 
>>>>>> That's ok. If you want to support only OpenShift than do so.
>>>>> 
>>>>> I think you missed my point. An OpenShift template can be used on
>>>>> any Kubernetes environment at all - including Atomic and GKE. Since
>>>>> an OpenShift template is a client side preprocessor; it outputs
>>>>> vanilla Kubernetes JSON
>>> 
>>> Aren't templates actually processed server side? I've just tried processing
>>> it without a connection to a running master & the client throws an error
>>> trying to post to /osapi/v1beta3/templateConfigs.
>> 
>> Ah is that new in v1beta3? Either way, doing a bit of search/replace on some
>> property expressions in the JSON is pretty trivial to do client side right?
> 
> No that's from day 1 I believe but I will defer to someone from OpenShift to correct me if I'm wrong. I'm not sure why that decision was made, but of course it would be trivial to do client side, including the generation of values, as opposed to just specifying values on cmd line. Templates can also be stored server side for easier sharing too which is definitely a nice feature - basically it's the beginnings of an app store I guess.

We'll probably add transformation to the client - it is just simple transformations.

The reason it's on the server was so that different clients didn't need to reimplement it.

> 
>> 
>> James
>> -------
>> Red Hat
>> 
>> Twitter: @jstrachan
>> Email: jstracha at redhat.com <mailto:jstracha at redhat.com>
>> Blog: http://macstrac.blogspot.com/ <http://macstrac.blogspot.com/>
>> 
>> hawtio: http:/ <http://fusesource.com/>/hawt.io/ <http://hawt.io/>
>> fabric8: http:/ <http://fusesource.com/>/fabric8.io/ <http://fabric8.io/>
>> 
>> Open Source Integration