<div dir="ltr">Hey Andrea!<div><br></div><div>Exactly! One of the most important use cases is Kubernetes. </div><div><br></div><div>I also absolutely agree - per cache and per cache manager level sounds reasonable.</div><div><br></div><div>Thanks</div><div>Sebastian</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 26, 2016 at 8:25 AM, Andrea Cosentino <span dir="ltr"><<a href="mailto:ancosen1985@yahoo.com" target="_blank">ancosen1985@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:13px"><div><span>Hi Sebastian,</span></div><div><span><br></span></div><div><span>This type of feature can be very useful for liveness and readiness probes in a Kubernetes cluster [1].</span></div><div><span><br></span></div><div><span>Maybe you can think at check status per-cache but also at whole server level.</span></div><div><span><br></span></div><div dir="ltr"><span>[1] </span><a href="http://kubernetes.io/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks" target="_blank">http://kubernetes.io/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks</a></div><div dir="ltr"><br></div><div dir="ltr">Thanks!</div><div></div><div> </div><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">--</div><div dir="ltr">Andrea Cosentino </div><div dir="ltr">----------------------------------</div><div dir="ltr">Apache Camel PMC Member</div><div dir="ltr">Apache Karaf Committer</div><div dir="ltr">Apache Servicemix Committer</div><div dir="ltr">Email: <a href="mailto:ancosen1985@yahoo.com" target="_blank">ancosen1985@yahoo.com</a></div><div dir="ltr">Twitter: @oscerd2</div><div dir="ltr">Github: oscerd</div></div></div></div></div> <div><br><br></div><div style="display:block"> <div style="font-family:Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:13px"> <div style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div><div class="h5"> <div dir="ltr"><font size="2" face="Arial"> On Tuesday, July 26, 2016 7:11 AM, Sebastian Laskawiec <<a href="mailto:slaskawi@redhat.com" target="_blank">slaskawi@redhat.com</a>> wrote:<br></font></div> <br><br> </div></div><div><div><div class="h5"><div><div dir="ltr">Dear Community,<div><br></div><div>I'd like to ask you for help. I'm currently sketching a design for a REST health check endpoint for Infinispan and I'm trying to imagine possible use cases. </div><div><br></div><div>Could you please give me a hand and tell me what functionalities are important for you? Would you like to be able to check status per-cache or maybe a red (not healthy), green (healthy), yellow (healthy, rebalance in progress) cluster status is sufficient? What kind of information do you expect to be there?</div><div><br></div><div>Thanks</div><div>Sebastian</div></div></div><br></div></div>_______________________________________________<br>infinispan-dev mailing list<br><a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br><br></div> </div> </div> </div></div></div><br>_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br></blockquote></div><br></div>