[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nginx
Subject:    Re: FRiCKLE Labs & MegiTeam pres. ngx_supervisord
From:       Roger Hoover <roger.hoover () gmail ! com>
Date:       2009-10-29 23:38:14
Message-ID: 44cb1ba30910291638s54dab8fdxde4cb47950e768ac () mail ! gmail ! com
[Download RAW message or body]

This is exciting.  Thanks for contributing it.

Roger

2009/10/28 Piotr Sikora <piotr.sikora@frickle.com>

> Hello,
> I'm proud to present a module, already mentioned on the list a few days ago
> by Grzegorz Nosek, that provides nginx with API to communicate with
> supervisord.
>
> Initial release adds the ability to START and STOP backends (or any
> programs) on demand. If supervisord's [program:backend0] entry is configured
> with "startsecs" parameter, then supervisord (and ngx_supervisord) will wait
> that time before returning successful or failed status. This is of course
> done in asynchronous way, so it doesn't halt nginx for a moment.
>
> This simple feature, combined with load-aware load balancers (like Grzegorz
> Nosek's nginx-upstream-fair) can offer very powerful features (starting
> first backend when the first request arrives, starting/stopping backends on
> demand, depending on the load, etc, etc). Patch for nginx-upstream-fair is
> included in the release and it shows how easy all of this can be achieved.
>
> Current version allows only one module to "register" its monitors with
> ngx_supervisord, but as soon as there will be need for more (read: other
> modules will start using ngx_supervisord), this will be changed without any
> changes in the API.
>
> If something is unclear, just ask.
>
>
> This module was fully funded by megiteam.pl
>
> For more information, API specification & download please visit:
> http://labs.frickle.com/nginx_ngx_supervisord/
>
>
> Best regards,
> Piotr Sikora < piotr.sikora@frickle.com >
>
>
>

[Attachment #3 (text/html)]

This is exciting.  Thanks for contributing it.<br><br>Roger<br><br><div \
class="gmail_quote">2009/10/28 Piotr Sikora <span dir="ltr">&lt;<a \
href="mailto:piotr.sikora@frickle.com">piotr.sikora@frickle.com</a>&gt;</span><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> Hello,<br>
I&#39;m proud to present a module, already mentioned on the list a few days ago by \
Grzegorz Nosek, that provides nginx with API to communicate with supervisord.<br> \
<br> Initial release adds the ability to START and STOP backends (or any programs) on \
demand. If supervisord&#39;s [program:backend0] entry is configured with \
&quot;startsecs&quot; parameter, then supervisord (and ngx_supervisord) will wait \
that time before returning successful or failed status. This is of course done in \
asynchronous way, so it doesn&#39;t halt nginx for a moment.<br>

<br>
This simple feature, combined with load-aware load balancers (like Grzegorz \
Nosek&#39;s nginx-upstream-fair) can offer very powerful features (starting first \
backend when the first request arrives, starting/stopping backends on demand, \
depending on the load, etc, etc). Patch for nginx-upstream-fair is included in the \
release and it shows how easy all of this can be achieved.<br>

<br>
Current version allows only one module to &quot;register&quot; its monitors with \
ngx_supervisord, but as soon as there will be need for more (read: other modules will \
start using ngx_supervisord), this will be changed without any changes in the \
API.<br>

<br>
If something is unclear, just ask.<br>
<br>
<br>
This module was fully funded by <a href="http://megiteam.pl" \
target="_blank">megiteam.pl</a><br> <br>
For more information, API specification &amp; download please visit:<br>
<a href="http://labs.frickle.com/nginx_ngx_supervisord/" \
target="_blank">http://labs.frickle.com/nginx_ngx_supervisord/</a><br> <br>
<br>
Best regards,<br><font color="#888888">
Piotr Sikora &lt; <a href="mailto:piotr.sikora@frickle.com" \
target="_blank">piotr.sikora@frickle.com</a> &gt;<br> <br>
<br>
</font></blockquote></div><br>



[prev in list] [next in list] [prev in thread] [next in thread]