[
https://jira.jboss.org/jira/browse/TEIID-442?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-442.
----------------------------------
Resolution: Done
Simplified to a single configuration (we may still want to use the term
"current" rather than "next startup"). The config.xml still needs to
have requiresrestart expanded - and the console should do a better job of information the
user of restart requirements.
Simplify configuration mechanics
--------------------------------
Key: TEIID-442
URL:
https://jira.jboss.org/jira/browse/TEIID-442
Project: Teiid
Issue Type: Task
Components: Common, Console, Server
Affects Versions: 6.1.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 6.1.0
The current differentiation between start up and next startup is tenuous. After talking
with Van and Ramesh a better simplified approach is to have a single live configuration,
which essentially removes the notion of a startup configuration. As configuration changes
are made, TEIID-441 will do a better job of informing the admin what should be restarted.
When a host controller is asked to start processes it will save the current state of the
configuration to the filesystem. And instead of keeping a single backup, we'll keep
some rotating number of them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira