8:38 p.m.
Brian Stansberry created AS7-4383:
-------------------------------------
Summary: Mode to disable writing deployment outcome files to deployment
scanner dir
Key: AS7-4383
URL: https://issues.jboss.org/browse/AS7-4383
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
Investigate adding a config option that disables writing the .isdeploying, .deployed,
.isundeploying, .undeployed files to the deployment scanner dir.
Idea is to make it possible to have multiple scanners on different nodes sharing the
deployment directory, without having the markers from one interfere with another.
This may not be practical at all in reality; needs investigation.
Marker files created by the user to control deployment should still be supported.
The .failed and .pending files are a bit of a gray area that need investigation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:25 p.m.
[
https://issues.jboss.org/browse/AS7-4383?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-4383:
---------------------------------------
Another option is to have the switch trigger storing the files in the data/ dir, so they
are usable by the scanner code but are not visible to the user. This would add quite a bit
of complexity to the scanning logic though.
Mode to disable writing deployment outcome files to deployment
scanner dir
--------------------------------------------------------------------------
Key: AS7-4383
URL: https://issues.jboss.org/browse/AS7-4383
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
Investigate adding a config option that disables writing the .isdeploying, .deployed,
.isundeploying, .undeployed files to the deployment scanner dir.
Idea is to make it possible to have multiple scanners on different nodes sharing the
deployment directory, without having the markers from one interfere with another.
This may not be practical at all in reality; needs investigation.
Marker files created by the user to control deployment should still be supported.
The .failed and .pending files are a bit of a gray area that need investigation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:44 a.m.
[
https://issues.jboss.org/browse/AS7-4383?page=com.atlassian.jira.plugin.s...
]
Bela Ban commented on AS7-4383:
-------------------------------
Another suggestion would be to copy the application to a dir (specific to the server)
under 'data', and keep the marker in the same directory as well.
Having shared deployments used to work in previous versions (6,5,4) of AS.
Mode to disable writing deployment outcome files to deployment
scanner dir
--------------------------------------------------------------------------
Key: AS7-4383
URL: https://issues.jboss.org/browse/AS7-4383
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
Investigate adding a config option that disables writing the .isdeploying, .deployed,
.isundeploying, .undeployed files to the deployment scanner dir.
Idea is to make it possible to have multiple scanners on different nodes sharing the
deployment directory, without having the markers from one interfere with another.
This may not be practical at all in reality; needs investigation.
Marker files created by the user to control deployment should still be supported.
The .failed and .pending files are a bit of a gray area that need investigation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:27 a.m.
[
https://issues.jboss.org/browse/AS7-4383?page=com.atlassian.jira.plugin.s...
]
Dimitris Andreadis commented on AS7-4383:
-----------------------------------------
I think those changes just screw up completely the way the new scanner is supposed to
work. Either you have marker files, or you don't.
IMO, we should have 2 deployment scanner types, new style and old style, and be able to
configure them independently.
Mode to disable writing deployment outcome files to deployment
scanner dir
--------------------------------------------------------------------------
Key: AS7-4383
URL: https://issues.jboss.org/browse/AS7-4383
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
Investigate adding a config option that disables writing the .isdeploying, .deployed,
.isundeploying, .undeployed files to the deployment scanner dir.
Idea is to make it possible to have multiple scanners on different nodes sharing the
deployment directory, without having the markers from one interfere with another.
This may not be practical at all in reality; needs investigation.
Marker files created by the user to control deployment should still be supported.
The .failed and .pending files are a bit of a gray area that need investigation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 a.m.
[
https://issues.jboss.org/browse/AS7-4383?page=com.atlassian.jira.plugin.s...
]
Emanuel Muckenhuber commented on AS7-4383:
------------------------------------------
Hmm, yeah perhaps the old mode with additional .ignore markers could be enough.
Mode to disable writing deployment outcome files to deployment
scanner dir
--------------------------------------------------------------------------
Key: AS7-4383
URL: https://issues.jboss.org/browse/AS7-4383
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
Investigate adding a config option that disables writing the .isdeploying, .deployed,
.isundeploying, .undeployed files to the deployment scanner dir.
Idea is to make it possible to have multiple scanners on different nodes sharing the
deployment directory, without having the markers from one interfere with another.
This may not be practical at all in reality; needs investigation.
Marker files created by the user to control deployment should still be supported.
The .failed and .pending files are a bit of a gray area that need investigation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:40 p.m.
[
https://issues.jboss.org/browse/AS7-4383?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-4383.
-----------------------------------
Fix Version/s: No Release
(was: 7.2.0.Alpha1)
Resolution: Won't Fix
If a user uses the CLI or admin console to undeploy a deployment added by the scanner, we
put down an .undeployed marker to record that, so the scanner doesn't just come along
and deploy it again. So this JIRA would break that functionality, plus probably others.
Mode to disable writing deployment outcome files to deployment
scanner dir
--------------------------------------------------------------------------
Key: AS7-4383
URL: https://issues.jboss.org/browse/AS7-4383
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: No Release
Investigate adding a config option that disables writing the .isdeploying, .deployed,
.isundeploying, .undeployed files to the deployment scanner dir.
Idea is to make it possible to have multiple scanners on different nodes sharing the
deployment directory, without having the markers from one interfere with another.
This may not be practical at all in reality; needs investigation.
Marker files created by the user to control deployment should still be supported.
The .failed and .pending files are a bit of a gray area that need investigation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4459
days inactive
4660
days old
5 comments
4 participants
participants (4)
-
Bela Ban (JIRA) -
Brian Stansberry (JIRA)
-
Dimitris Andreadis (JIRA)
-
Emanuel Muckenhuber (JIRA)