zevenet/zlb repository overview

⁠ZEVENET Load Balancer⁠

This is the docker repository of ZEVENET Load Balancer Community Edition

Load Balancing is the process of distributing data across real resources to provide redundancy, reliability, and improve performance.

In addition, ZEVENET Load Balancer will help you Scale easy and avoid system disruptions with the Application Delivery Controller challengers through high availability, load balancing, security and high performance.

• Security Secure and protect the access of applications through low level defense, encryption and application firewall.

• High Availability Create high availability infrastructure for WAN access, applications and services for local and global datacenters.

• Scalability Scale and automate growth of networks and servers with traffic control schedulers and programmable interfaces.

• High Performance Cutting-edge technology for the most accessible and multi platform ADC solution in the market.

⁠Deploy ZEVENET

If you already have a running docker containers environment you just need to execute the following command to install ZEVENET Load Balancer

docker pull zevenet/zlb

When ZEVENET docker container is up and running the Grafical User Interface should be reachable from any web browser localy on this URL and Port:

https://localhost:444

Please, note that it is an HTTPS url instead of http

User: root Password: admin

For security reasons change the default password

If you plan to create farms you will need to expose the correspondig ports in the “docker run” command. For example, to run a web server backend on port 80 and 443 your “docker run” command would be:

docker run --cap-add=NET_ADMIN --name zlb -p 444:444 -p 80:80 -p 443:443 -itd zevenet/zlb /bin/bash

For further information, please, follow this link:

# Dockerizing ZEVENET CE⁠

Additionally we have a GitHub repository where the community can contribute to the development of this software.

⁠How to Contribute

You can contribute with the evolution of the ZEVENET Load Balancer in a wide variety of ways:

• Creating content: Documentation in the GitHub project wiki⁠, doc translations, documenting source code, etc.
• Help to other users through the mailing lists.
• Reporting and Resolving Bugs from the GitHub project Issues⁠.
• Development of new features.

⁠Reporting Bugs

Please use the GitHub project Issues⁠ to report any issue or bug with the software. Try to describe the problem and a way to reproduce it. It'll be useful to attach the service and network configurations as well as system and services logs.

⁠Development & Resolving Bugs

In order to commit any change, as new features, bug fix or improvement, just perform a git clone of the repository, git add when all the changes has been made and git commit when you're ready to send the change.

During the submit, please ensure that every change is associated to a logical change in order to be easily identified every change.

In the commit description please use the following format:

[CATEGORY] CHANGE_SHORT_DESCRIPTION

OPTIONAL_LONGER_DESCRIPTION

SIGNED_OFFS

MODIFIED_FILES

Where:

• CATEGORY is either: Bugfix for resolving bugs or issues, Improvement for enhancements of already implemented features or New Feature for new developments that provides a new feature not implemented before.
• CHANGE_SHORT_DESCRIPTION is a brief description related with the change applied and allows to identify easily such modification. If it's related to a bug included in the Issues section it's recommended to include the identification reference for such bug.
• OPTIONAL_LONGER_DESCRIPTION is an optional longer description to explain details about the change applied.
• SIGNED_OFFS is the Signed-off-by entry where the username followed by the email can be placed.
• MODIFIED_FILES are the list of files that hace been modified, created or deleted with the commit.

Usually, executing git commit -a -s will create the fields described above.

Finally, just execute a git push and request a pull of your changes. In addition, you can use git format-patch to create your patches and send them through the official distribution list.

⁠Creating & Updating Documentation or Translations

In the official GitHub wiki⁠ there is available a list of pages and it's translations. Please clone the wiki, apply your changes and request a pull in order to be applied.

⁠Helping another Users

The official distribution list could be accessed through the zevenet-ce-users google group⁠.

To post in this group, send email to [email protected]⁠.

But you need to request a join first into the group by sending an email to [email protected]⁠.

To unsubscribe from this group, send email to [email protected]⁠

For more options, visit https://groups.google.com/a/zevenet.com/d/optout⁠

⁠www.zevenet.com⁠