e1fc0b8734
commit 48a0b902b67da46f1eed4afa687bdcb56b59d02f
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Mon Dec 16 15:35:07 2019 +0200
Increase timouts in the mxs173_trottle_filter test
commit 81d8083a89421a8004b8024d480ae0f35d715b86
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Mon Dec 16 14:19:39 2019 +0200
Increase timeouts in max1071_maxrow test
commit e1039c6132f0e9274b8801165f3f905ede7c9421
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Mon Dec 16 00:06:53 2019 +0200
Remove hardcoded 'home/vagrant/' from all maxscale.cnf in system tests
commit 28c8029e060afdcf5159bf802b13dcd5e484d9f1
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sun Dec 15 21:31:34 2019 +0200
Use private IP for Galera congiguration in maxscale-system-tests
commit 66dc36cbf43a5fb92465df31e1295e82865be1fc
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sun Dec 15 09:06:28 2019 +0200
Fix typos in fwf_*.cpp
commit 44c7a4384ddf39596c0254c955aeb6c008a00a35
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sun Dec 15 09:05:26 2019 +0200
Fix typos in fwf_*.cpp
commit 2649017611908a8b0d27090f49722947ac31c4f4
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sun Dec 15 09:03:41 2019 +0200
Fix typos in fwf_*.cpp
commit 5cc87658523e8496eaab17700be8a821af5b0cde
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sat Dec 14 23:54:53 2019 +0200
Fix typo in fwf_copy_rules.cpp
commit fb1accc36cb9d79691469f63cb4535f3bc38dedd
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sat Dec 14 23:52:51 2019 +0200
More hardcoded 'vagrant' removals
commit 77e49d474b4abe767629ff87b01f08137773d761
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sat Dec 14 23:35:09 2019 +0200
Fix hardcoded 'vagrant' user in fwf* tests
Several firewall filter tests has hardcoded 'vagrant' as a user name for
access user on the VM. Changed to node->access_user.
commit ed5ab1487f37822db6a7478f76c0f3652776c389
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sat Dec 14 22:50:35 2019 +0200
Fix IP vs IP_private
Many tests use IP instead of IP_private which makes them failed in the
AWS or GCloud environment.
The same applies to get_conn_num() etc functions.
commit 0558aac23d303a675dc12d05b1766e698753b444
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Thu Aug 15 12:02:01 2019 +0300
fix IP -> IP_private for some mysqlmon* testst
commit 5d9c70970d970eb995c8774d0088bd1c54ab76fe
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Sat Dec 14 20:20:51 2019 +0200
Replace IP to IP_private in the maxscale-system-tests
commit b06cf3329af59ff100748691991213fe639f29e6
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Tue Nov 19 11:52:33 2019 +0200
Remove spaces from value which were read from *_network_config
MDBCI can put spaces around values in the *_network_config file which
can cause ssh connection failures in the tests. To fix it removing all
spaces from all values which were read from *_network_config
commit b3904f019847ef1db9d4ec9714ad9ef869fa0b01
Author: Timofey Turenko <timofey.turenko@mariadb.com>
Date: Thu Dec 12 23:36:31 2019 +0200
Increate default timeout for all system tests
MaxScale by MariaDB Corporation
The MariaDB Corporation MaxScale is an intelligent proxy that allows forwarding of database statements to one or more database servers using complex rules, a semantic understanding of the database statements and the roles of the various servers within the backend cluster of databases.
MaxScale is designed to provide load balancing and high availability functionality transparently to the applications. In addition it provides a highly scalable and flexible architecture, with plugin components to support different protocols and routing decisions.
For a detailed overview of what MaxScale can do, read the MaxScale page on the MariaDB website.
An Google Group exists for MaxScale that can be used to discuss ideas, issues and communicate with the MaxScale community.
We're also on the #maria and #maxscale channels on FreeNode.
Please report all feature requests, improvements and bugs in the MariaDB Jira.
Getting Started
Read the Documentation Overview for a list of all MaxScale documents.
Documentation
The official documentation can be found on the MariaDB Knowledge Base.
A MaxScale Troubleshooting Guide can be found on the MariaDB Knowledgebase. It answers common questions encountered when installing and using MaxScale.
The documentation can also be found in the Documentation directory of the source tree.
Contributing Code
Read the Contributing page on the wiki for more information on how to do pull request and where to do them.