Use shared directory for Fuse binary content -------------------------------------------- Key: JBESB-3970 URL: https://issues.jboss.org/browse/JBESB-3970 Project: JBoss ESB Issue Type: Enhancement Security Level: Public(Everyone can see) Reporter: Ben Parees The Fuse RPM cartridge is embedding a zip of the Fuse product, and then on each app creation, it extracts the zip within the user's gear. What it should be doing is 1) embedding the Fuse product in an extracted form 2) using the "fuse/usr" path so it's not copied into every user's gear (Openshift will link contents in the cartridge usr directory into the user's gear, rather than copying those files) That would reduce the time required to create new fuse apps, and reduce the quota usage required for each gear. In addition, the current mechanism restricts the ability to path the Fuse product binaries at the node level (since each gear has its own copy of them now which will have to be patched in case of any security issues) It has been noted by the Fuse team that due to the way patching and configuration are handled, some thought needs to go into what can be put into a shared (and not user modifiable) directory versus what can be created as read-only (from the user perspective) files. Some changes to the Fuse patching logic may be required in addition to restructuring the cartridge RPM.