[jboss-jira] [JBoss JIRA] (WFCORE-919) Allow read-only data/content storage

[James Livingston (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Livingston updated WFCORE-919:
------------------------------------
    Description: 
It would be nice to allow the content repository to be read-only, if there was an external guarantee that all content should be there. This would be useful in situations where all HCs (including the DC) share that over NFS, or deployments are managed via another system (docker, puppet etc).

It could be a ContentRepository implementation which does not make chances, and fails if attempted or content is missing. On read-only HCs the current writeability check would need to be disabled, along with the cleaner task, and the DC (if it could write) would need to ensure content was not removed prior to HCs performing undeployment.


This would presumably have some interaction with WFCORE-310.

  was:
It would be nice to allow the content repository to be read-only, if there was an external guarantee that all content should be there. This would be useful in situations where all HCs (including the DC) share that over NFS, or deployments are managed via another system (docker, puppet etc).

It could be a ContentRepository implementation which does not make chances, and fails if attempted or content is missing. On read-only HCs the current writeability check would need to be disabled, along with the cleaner task, and the DC (if it could write) would need to ensure content was not removed prior to HCs performing undeployment.



> Allow read-only data/content storage
> ------------------------------------
>
>                 Key: WFCORE-919
>                 URL: https://issues.jboss.org/browse/WFCORE-919
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>    Affects Versions: 2.0.0.Beta4
>            Reporter: James Livingston
>            Assignee: Brian Stansberry
>
> It would be nice to allow the content repository to be read-only, if there was an external guarantee that all content should be there. This would be useful in situations where all HCs (including the DC) share that over NFS, or deployments are managed via another system (docker, puppet etc).
> It could be a ContentRepository implementation which does not make chances, and fails if attempted or content is missing. On read-only HCs the current writeability check would need to be disabled, along with the cleaner task, and the DC (if it could write) would need to ensure content was not removed prior to HCs performing undeployment.
> This would presumably have some interaction with WFCORE-310.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)