[MXS-1300] Implement MaxCtrl Created: 2017-06-28  Updated: 2017-08-09  Resolved: 2017-07-27

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: 2.2.0

Type: Task Priority: Major
Reporter: Johan Wikman Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2017-37, 2017-38

 Description   

Implement MaxCtrl - the MaxScale administration tool that uses the new REST-API.

  • Everything that is available and modifiable via the current maxadmin should be available and modifiable via maxctrl.
  • Maxctrl must be able to connect to more MaxScale instances than one.
  • Maxctlr must be able to make modifications simultaneously to several MaxScale instances at once (some measures should be taken to reduce the risk that modifications inadvertently are made when one of the MaxScale instances is down or unreachable, e.g. first ping both before actually performing the command).
  • Maxctrl must be able to visualize the data from several MaxScale instances in a manner that makes it straightforward for a user to spot discrepancies.
  • Even if Maxctrl is connected to multiple MaxScale instances it must be possible to explicitly make modifications to a specific instance (e.g. to fix noticed discrepancies).


 Comments   
Comment by markus makela [ 2017-07-27 ]

It is now possible to substitute MaxAdmin with MaxCtrl.

Generated at Thu Feb 08 04:05:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.