Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/openresty/lua-upstream-nginx-module

Nginx C module to expose Lua API to ngx_lua for Nginx upstreams
https://github.com/openresty/lua-upstream-nginx-module

Last synced: 10 days ago
JSON representation

Nginx C module to expose Lua API to ngx_lua for Nginx upstreams

Awesome Lists containing this project

README 

        
Name

====



ngx_http_lua_upstream - Nginx C module to expose Lua API to ngx_lua for Nginx upstreams



Table of Contents

=================



* [Name](#name)

* [Status](#status)

* [Synopsis](#synopsis)

* [Functions](#functions)

    * [get_upstreams](#get_upstreams)

    * [get_servers](#get_servers)

    * [get_primary_peers](#get_primary_peers)

    * [get_backup_peers](#get_backup_peers)

    * [set_peer_down](#set_peer_down)

    * [current_upstream_name](#current_upstream_name)

* [TODO](#todo)

* [Compatibility](#compatibility)

* [Installation](#installation)

* [Author](#author)

* [Copyright and License](#copyright-and-license)

* [See Also](#see-also)



Status

======



This module is production ready.



Synopsis

========



```nginx

http {

    upstream foo.com {

        server 127.0.0.1 fail_timeout=53 weight=4 max_fails=100;

        server agentzh.org:81;

    }



    upstream bar {

        server 127.0.0.2;

    }



    server {

        listen 8080;



        # sample output for the following /upstream interface:

        # upstream foo.com:

        #     addr = 127.0.0.1:80, weight = 4, fail_timeout = 53, max_fails = 100

        #     addr = 106.184.1.99:81, weight = 1, fail_timeout = 10, max_fails = 1

        # upstream bar:

        #     addr = 127.0.0.2:80, weight = 1, fail_timeout = 10, max_fails = 1



        location = /upstreams {

            default_type text/plain;

            content_by_lua_block {

                local concat = table.concat

                local upstream = require "ngx.upstream"

                local get_servers = upstream.get_servers

                local get_upstreams = upstream.get_upstreams



                local us = get_upstreams()

                for _, u in ipairs(us) do

                    ngx.say("upstream ", u, ":")

                    local srvs, err = get_servers(u)

                    if not srvs then

                        ngx.say("failed to get servers in upstream ", u)

                    else

                        for _, srv in ipairs(srvs) do

                            local first = true

                            for k, v in pairs(srv) do

                                if first then

                                    first = false

                                    ngx.print("    ")

                                else

                                    ngx.print(", ")

                                end

                                if type(v) == "table" then

                                    ngx.print(k, " = {", concat(v, ", "), "}")

                                else

                                    ngx.print(k, " = ", v)

                                end

                            end

                            ngx.print("\n")

                        end

                    end

                end

            }

        }

    }

}

```



Functions

=========



[Back to TOC](#table-of-contents)



get_upstreams

-------------

`syntax: names = upstream.get_upstreams()`



Get a list of the names for all the named upstream groups (i.e., explicit `upstream {}` blocks).



Note that implicit upstream groups created by `proxy_pass` and etc are excluded.



[Back to TOC](#table-of-contents)



get_servers

-----------

`syntax: servers = upstream.get_servers(upstream_name)`



Get configurations for all the servers in the specified upstream group. Please note that one server may take multiple addresses when its server name can be resolved to multiple addresses.



The return value is an array-like Lua table. Each table entry is a hash-like Lua table that takes the following keys:



* addr



    socket address(es). can be either a Lua string or an array-like Lua table of Lua strings.

* backup

* fail_timeout

* max_fails

* name

* weight



[Back to TOC](#table-of-contents)



get_primary_peers

-----------------

`syntax: peers = upstream.get_primary_peers(upstream_name)`



Get configurations for all the primary (non-backup) peers in the specified upstream group.



The return value is an array-like Lua table for all the primary peers. Each table entry is a (nested) hash-like Lua table that takes the following keys:



* current_weight

* effective_weight

* fail_timeout

* fails

* id



    Identifier (ID) for the peer. This ID can be used to reference a peer in a group in the peer modifying API.

* max_fails

* name



    Socket address for the current peer

* weight

* accessed



    Timestamp for the last access (in seconds since the Epoch)

* checked



    Timestamp for the last check (in seconds since the Epoch)

* down



    Holds true if the peer has been marked as "down", otherwise this key is not present

* conns



    Number of active connections to the peer (this requires NGINX 1.9.0 or above).



[Back to TOC](#table-of-contents)



get_backup_peers

----------------

`syntax: peers = upstream.get_backup_peers(upstream_name)`



Get configurations for all the backup peers in the specified upstream group.



The return value has the same structure as [get_primary_peers](#get_primary_peers) function.



[Back to TOC](#table-of-contents)



set_peer_down

-------------

`syntax: ok, err = upstream.set_peer_down(upstream_name, is_backup, peer_id, down_value)`



Set the "down" (boolean) attribute of the specified peer.



To uniquely specify a peer, you need to specify the upstream name, whether or not it is a backup peer, and the peer id (starting from 0).



Note that this method only changes the peer settings in the current Nginx worker

process. You need to synchronize the changes across all the Nginx workers yourself if you

want a server-wide change (for example, by means of [ngx_lua](https://github.com/openresty/lua-nginx-module#ngxshareddict)'s [ngx.shared.DICT](https://github.com/openresty/lua-nginx-module#ngxshareddict)).



Below is an example. Consider we have a "bar" upstream block in `nginx.conf`:



```nginx

upstream bar {

    server 127.0.0.2;

    server 127.0.0.3 backup;

    server 127.0.0.4 fail_timeout=23 weight=7 max_fails=200 backup;

}

```



then



```lua

upstream.set_peer_down("bar", false, 0, true)

```



will turn down the primary peer corresponding to `server 127.0.0.2`.



Similarly,



```lua

upstream.set_peer_down("bar", true, 1, true)

```



will turn down the backup peer corresponding to `server 127.0.0.4 ...`.



You can turn on a peer again by providing a `false` value as the 4th argument.



[Back to TOC](#table-of-contents)



current_upstream_name

---------------------

`syntax: name = upstream.current_upstream_name()`



Returns the name of the proxied upstream for the current request.

If there is no upstream for this request (no `proxy_pass` call), or this

function is called in a phase prior to the content phase, then the return value

will be `nil`. If a port is explicitly included in the upstream definition or

`proxy_pass` directive, it will be included in the return value of this function.



Example:



```lua

-- upstream my_upstream { ... }

-- proxy_pass http://my_upstream;

upstream.current_upstream_name() --> my_upstream



-- proxy_pass http://example.com:1234;

upstream.current_upstream_name() --> example.com:1234

```



Note that implicit upstreams created by `proxy_pass` are included, contrary to

the output of `upstream.get_upstreams()`.



[Back to TOC](#table-of-contents)



TODO

====



* Add API to add or remove servers to existing upstream groups.



[Back to TOC](#table-of-contents)



Compatibility

=============



The following versions of Nginx should work with this module:



* **1.11.x** (last tested: 1.11.2)

* **1.10.x**

* **1.9.x**  (last tested: 1.9.15)

* **1.8.x**

* **1.7.x**  (last tested: 1.7.10)

* **1.6.x**

* **1.5.x**  (last tested: 1.5.12)



[Back to TOC](#table-of-contents)



Installation

============



This module is bundled and enabled by default in the [OpenResty](http://openresty.org) bundle. And you are recommended to use OpenResty.



1. Grab the nginx source code from [nginx.org](http://nginx.org/), for example,

the version 1.11.2 (see [nginx compatibility](#compatibility)),

2. then grab the source code of the [ngx_lua](https://github.com/openresty/lua-nginx-module#installation) as well as its dependencies like [LuaJIT](http://luajit.org/download.html).

3. and finally build the source with this module:



```bash

wget 'http://nginx.org/download/nginx-1.11.2.tar.gz'

tar -xzvf nginx-1.11.2.tar.gz

cd nginx-1.11.2/



# assuming your luajit is installed to /opt/luajit:

export LUAJIT_LIB=/opt/luajit/lib



# assuming you are using LuaJIT v2.1:

export LUAJIT_INC=/opt/luajit/include/luajit-2.1



# Here we assume you would install you nginx under /opt/nginx/.

./configure --prefix=/opt/nginx \

    --with-ld-opt="-Wl,-rpath,$LUAJIT_LIB" \

    --add-module=/path/to/lua-nginx-module \

    --add-module=/path/to/lua-upstream-nginx-module



make -j2

make install

```



Starting from NGINX 1.9.11, you can also compile this module as a dynamic module, by using the `--add-dynamic-module=PATH` option instead of `--add-module=PATH` on the

`./configure` command line above. And then you can explicitly load the module in your `nginx.conf` via the [load_module](http://nginx.org/en/docs/ngx_core_module.html#load_module)

directive, for example,



```nginx

load_module /path/to/modules/ngx_http_lua_upstream_module.so;

```



[Back to TOC](#table-of-contents)



Author

======



Yichun "agentzh" Zhang (章亦春) , OpenResty Inc.



[Back to TOC](#table-of-contents)



Copyright and License

=====================



This module is licensed under the BSD license.



Copyright (C) 2014-2017, by Yichun "agentzh" Zhang, OpenResty Inc.



All rights reserved.



Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:



* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.



* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.



THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.



[Back to TOC](#table-of-contents)



See Also

========

* the ngx_lua module: http://github.com/openresty/lua-nginx-module#readme

* the [lua-resty-upstream-healthcheck](https://github.com/openresty/lua-resty-upstream-healthcheck) library which makes use of the Lua API provided by this module.



[Back to TOC](#table-of-contents)