Re: Three-tier application deployment on OpenShift origin

On Mon, May 9, 2016 at 9:02 AM, ABDALA Olga wrote: > > > > > *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 OpenSh

RE: Three-tier application deployment on OpenShift origin

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 mailto:olga.abd...@solucom.fr>> wrote: Hell

Re: Three-tier application deployment on OpenShift origin

f pods. What do you mean by "the application's 'versions'"? > > > Since you have builds, I am guessing that you used something like > "new-app". new-app will have created a deploymentconfig. You would want > to edit the deploymentconfig, find the p

RE: Three-tier application deployment on OpenShift origin

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 ha

RE: Three-tier application deployment on OpenShift origin

Hello Erik, Please find my comments inline De : Erik Jacobs [mailto:ejac...@redhat.com] Envoyé : 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

Re: Three-tier application deployment on OpenShift origin

It's just that the "zone=" label is discussed in our example scheduler configs used for service spreading so it has a technical significance. Using "env=" would be fine. On Wed, May 4, 2016 at 11:41 AM, Erik Jacobs w

Re: Three-tier application deployment on OpenShift origin

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 additionall

Re: Three-tier application deployment on OpenShift origin

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: ejacobsatredhat > Twitter: @

Re: Three-tier application deployment on OpenShift origin

*De :* Erik Jacobs [mailto:ejac...@redhat.com] > *Envoyé :* mardi 3 mai 2016 16:57 > *À :* ABDALA Olga > *Cc :* dev@lists.openshift.redhat.com > *Objet :* Re: Three-tier application deployment on OpenShift origin > > > > Hi Olga, > > > > Some responses inline/ &g

RE: Three-tier application deployment on OpenShift origin

configuration file, for me to specify the Node, please? Is it in the master-config.yaml file? Thank you! Olga De : Erik Jacobs [mailto:ejac...@redhat.com] Envoyé : mardi 3 mai 2016 16:57 À : ABDALA Olga Cc : dev@lists.openshift.redhat.com Objet : Re: Three-tier application deployment on OpenShift origin

Re: Three-tier application deployment on OpenShift origin

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: ejacobsatredhat Twitter: @ErikonOpen Freenode: thoraxe On Mon, Apr 25, 2016 at 9:34 AM, ABDALA Olga

Three-tier application deployment on OpenShift origin

Hello all, I am done with my origin advanced installation (thanks to your useful help) which architecture is composed of 4 virtualized servers (on the same network): - 1 Master - 2 Nodes - 1 VM hosting Ansible My next steps are to implement/test some use cases with a three-