Are you using any specific component? Or you have written something yourself?
David Strejc t: +420734270131 e: [email protected] On Thu, Feb 11, 2016 at 4:27 PM, Mateus Caruccio < [email protected]> wrote: > From my own experience, monitoring etcd is one way to do it, but requires > an extra component (the monitor) to be always up and running. > This monitor must have cluster roles, since it need to watch both project > and app (bc/dc) objects. > > The other way is to provide your users with templates containing all stuff > they will need. > > > *Mateus Caruccio* > Master of Puppets > +55 (51) 8298.0026 > gtalk: > > > *[email protected] <[email protected]>twitter: > @MateusCaruccio <https://twitter.com/MateusCaruccio>* > This message and any attachment are solely for the intended > recipient and may contain confidential or privileged information > and it can not be forwarded or shared without permission. > Thank you! > > On Thu, Feb 11, 2016 at 1:21 PM, David Strejc <[email protected]> > wrote: > >> Dear all, >> >> what is the best practise to trigger actions when I am creating >> application? >> >> Let's say I want to create database (as I am using external database >> cluster) and glusterfs volume for my application. >> >> Which approach should I look at? Should I make docker conteiner to ssh >> somewhere and let it trigger some scripts? >> >> Or is there any other way? Shoudl I somehow monitor etcd for app creation >> (as it was with activemq messages in Open Shift v2)? >> >> Thank you. >> >> David Strejc >> t: +420734270131 >> e: [email protected] >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
