Re: Three-tier application deployment on OpenShift origin

2016-05-09 Thread Erik Jacobs
é :* mercredi 4 mai 2016 17:32 > *À :* ABDALA Olga > *Cc :* dev@lists.openshift.redhat.com > *Objet :* Re: Three-tier application deployment on OpenShift origin > > > > > > On Wed, May 4, 2016 at 8:30 AM, ABDALA Olga <olga.abd...@solucom.fr> > wrote: >

RE: Three-tier application deployment on OpenShift origin

2016-05-09 Thread ABDALA Olga
De : Erik Jacobs [mailto:ejac...@redhat.com] Envoyé : lundi 9 mai 2016 14:31 À : ABDALA Olga Cc : dev@lists.openshift.redhat.com Objet : Re: Three-tier application deployment on OpenShift origin On Mon, May 9, 2016 at 4:56 AM, ABDALA Olga <olga.abd...@solucom.fr<mailto:olga.abd...@solu

RE: Three-tier application deployment on OpenShift origin

2016-05-09 Thread ABDALA Olga
Hello Luke and Erik, Please find my reaction inline De : Erik Jacobs [mailto:ejac...@redhat.com] Envoyé : mercredi 4 mai 2016 17:41 À : Luke Meyer Cc : ABDALA Olga; dev@lists.openshift.redhat.com Objet : Re: Three-tier application deployment on OpenShift origin Hi Luke, I'll have

Re: Three-tier application deployment on OpenShift origin

2016-05-04 Thread Erik Jacobs
Hi Luke, I'll have to disagree but only semantically. For a small environment and without changing the scheduler config, the concept of "zone" can be used. Yes, I would agree with you that in a real production environment the Red Hat concept of a "zone" is as you described. You could

Re: Three-tier application deployment on OpenShift origin

2016-05-04 Thread Luke Meyer
On Tue, May 3, 2016 at 10:57 AM, Erik Jacobs wrote: > Hi Olga, > > Some responses inline/ > > > Erik M Jacobs, RHCA > Principal Technical Marketing Manager, OpenShift Enterprise > Red Hat, Inc. > Phone: 646.462.3745 > Email: ejac...@redhat.com > AOL Instant Messenger: