[MXS-525] Dynamic configuration of MaxScale Created: 2016-01-07 Updated: 2016-11-22 Resolved: 2016-11-22 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Epic | Priority: | Major |
| Reporter: | markus makela | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | dynamic_configuration | ||
| Epic Name: | Dynamic Configuration of MaxScale |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2016-01-07 ] |
|
markus makela johan.wikman Please identify the fixVersion for various substasks. |
| Comment by Johan Wikman [ 2016-03-31 ] |
|
Moving to 1.5, even though it seems to be unlikely that it would be implemented to this extent. |
| Comment by Johan Wikman [ 2016-10-04 ] |
|
Moving to 2.1 although this is not what will be done. It's probably better to close this and recreate a new epic with the right set of tasks for 2.1. |
| Comment by Blake Smith [ 2016-10-27 ] |
|
This is definitely a feature we're very interested in for our production usage of MaxScale. Can anyone offer guidance or advice on starting points for this Epic? We'd like to help out however we can, but there's a lot of context we'd need to help with the work. |
| Comment by Dipti Joshi (Inactive) [ 2016-10-28 ] |
|
johan.wikman- Agree close this and create a new epic for the set of tasks for 2.1 |
| Comment by Johan Wikman [ 2016-10-28 ] |
|
The 2.1 tasks are modeled as feature |
| Comment by Johan Wikman [ 2016-11-22 ] |
|
This was created for 1.4. Either this is not relevant at the moment or there are now other tasks that covers this, so closing this as obsolete. |