Hi Bruno, As an alternative you could write your own Docker Volume Plugin ( https://docs.docker.com/engine/extend/plugins_volume/) to connect to your on-premise infrastructure and store the volumes containing the asset store, Solr data and PostgreSQL data there. But first think about the Docker image design and try running with "local" volumes.
Best regards, Tom [image: logo] *Tom Desair* *250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586* *Esperantolaan 4, Heverlee 3001, Belgium* www.atmire.com <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomd> 2016-03-01 16:19 GMT+01:00 Peter Dietz <[email protected]>: > Hi Bruno, > > There is no DSpace BitStore implementation for using Google Cloud Storage, > but the next release of DSpace has refactored the asset store plumbing to > allow for different implementations to be used. This advice might not be > very helpful for a current DSpace 5 instance, but would be helpful for a > development instance on DSpace 6, which adds under-the-hood improvements > that would help you better make use of Google Cloud Storage. > > The Interface for BitStore > > https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/storage/bitstore/BitStoreService.java > > Implementation to use AWS S3 storage. > > https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/storage/bitstore/S3BitStoreService.java > > If you are interested in adding Google Cloud Storage support just > implement a GoogleCloudStorageBitStoreService class and implement a few > methods: init, get, put, about, remove. > > Once you create a GCS implementation, then you can wire it in with some > spring bean xml. > > https://github.com/DSpace/DSpace/blob/master/dspace/config/spring/api/bitstore.xml > > We allow for a hybrid storage approach. Wire localStore to store#0, the > localStore would be seen as "local storage" even though you will be > mounting some remote NAS storage. Then wire the GCSStore to store#1, and > make that the incoming. Old assets on the NAS, new assets on GCS. > > > ________________ > Peter Dietz > Longsight > www.longsight.com > [email protected] > p: 740-599-5005 x809 > > On Tue, Mar 1, 2016 at 8:57 AM, Bruno Cabral <[email protected]> > wrote: > >> Hi Monika, >> >> Thank you! >> >> The idea is not having the databases inside the docker images. >> >> But is it possible to have the digital objects on a local netowrk >> attached storage while the dcoker is in Google Cloud, with dspace linking >> from the cloud to our NAS? >> >> And a mixed solution, having part of the objects on our NAS and other on >> Google Cloud Storage? >> >> Thanks and Regards, >> >> BC >> >> 2016-03-01 12:38 GMT-01:00 Monika Mevenkamp <[email protected]>: >> >>> I am not exactly sure either what the details are. But if you can make >>> your NAS storage visible inside the docker image such that you can link >>> /dspace/assetstore -> /NAS_assetstore >>> you should be fine. >>> >>> You need to think carefully about what you do with your database. >>> How do you plan to keep backups ? >>> >>> Keep in mind that, if you manage the database inside docker >>> you will not be able to upgrade software by building a new docker >>> image. Building a new image means loosing all data created/touched >>> inside the old image after that image was built and started. >>> >>> Monika >>> ________________ >>> Monika Mevenkamp >>> [email protected] >>> >>> http://mo-meven.tumblr.com/ >>> http://mcmprogramming.com/mo.meven/ >>> >>> >>> >>> On Feb 29, 2016, at 1:24 PM, Bruno Cabral <[email protected]> >>> wrote: >>> >>> Hi list, >>> >>> I'm member of a team that is developing and implementing a solution >>> using DSPACE. >>> >>> We intend that the apps including DSPACE stays on the Google Cloud >>> Infrastructure, in docker containers, and that the digital objects of the >>> DSPACE repository stay stored and linked on our local network Storage, on a >>> Network Attached Storage. >>> >>> Is this possible? How? >>> >>> Thanks, >>> >>> BC >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "DSpace Technical Support" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/dspace-tech. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
