My 2 cents is that we (Longsight) are rolling out our infrastructure with
Docker. We have java templates, tomcat, dspace templates. The DSpace
template builds on top of a tomcat template, which builds off of a java
template, which builds off of our base linux template. We're not done, but
its giving us predictability, and eventually fully automated deploys /
updates. Its complicated for the time being. Part of this terrifying
paradigm is that you design your application to survive instances dying.
i.e. Just assume that the database, solr, ES, postgres, nginx, tomcat, can
go down at any moment, and the application shouldn't lose data, and a
management tool should be able to quickly scale / restart things to bring
it all back up. This is probably more geared to an application that has
many instances of it running (one big unified DSpace application that holds
dozens of clients data). As opposed to an instance per client. It's
probably helpful to read up on building a 12 factor app
<http://12factor.net/>. Also, part of your instance setup is that
automation does everything, you should eventually be able to disable ssh
into your servers. Crazy huh?
The argument of Vagrant template being maintained by committers, well,
there's no reason that the DSpace community couldn't maintain docker
templates.
________________
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Thu, Jun 25, 2015 at 11:59 AM, Tim Donohue <tdono...@duraspace.org>
wrote:
> A few notes on this Vagrant v. Docker discussion...
>
> Vagrant is *specifically* built for development/testing environments. It's
> not recommended to use in Production. Take a look at how it's
> advertised...it's "Development environments made easy":
> https://www.vagrantup.com/ Vagrant is also a level of abstraction above
> Docker. It's about providing a "repeatable" virtual machine environment,
> and you can do so using Puppet (which is what vagrant-dspace uses), Chef,
> Ansible, or even Docker itself! That's right, Vagrant actually has a
> "Docker Provisioner" which lets you spin up a VM, auto-install Docker and
> one (or more) Docker containers.
> http://docs.vagrantup.com/v2/provisioning/docker.html
>
> Docker on the other hand is built more for Continuous Integration /
> Production environments. You could use it for a development environment,
> but it's more ideal for CI. That being said, you could use it *with*
> Vagrant...where you actually build a Docker container for your Production
> environment, but have the option of starting it via Vagrant for development
> / testing work.
>
> Here's an excellent answer to this question from the guy who wrote Vagrant
> on why comparing Vagrant to Docker is a bit like apples vs. oranges:
> http://stackoverflow.com/a/21314566/3750035
>
> My personal opinion here is that Docker is worth learning/using, IF you
> plan to use it in your Production environment. However, if you have no
> plans to use Docker in Production, then you may find it is easier to"mimic"
> your existing production server by just using Vagrant.
>
> Currently, we do NOT have a centrally managed DSpace Docker container (so
> anything out there is third-party built...so mileage may vary). But we do
> obviously provide vagrant-dspace (which is maintained by Committers, as
> several of us use it for development/testing of DSpace).
> https://github.com/DSpace/vagrant-dspace
>
> - Tim
>
>
> On 6/23/2015 4:57 PM, Monika C. Mevenkamp wrote:
>
> Hi
>
> my boss discovered a dspace docker
>
> so which one should I do - docker or vagrant ?
>
> They sound awfully alike
> the host can connect to things : tomcat / ssh / ...
> files can be shared between host and vagrant/docker guest
> it appears to be easy to hand a ‘vagrant’ or a ‘docker’ to another
> developer
>
> so what’s the deal ?
> why one over the other ?
>
> Monika
>
> —
> Monika Mevenkamp
> Digital Repository Infrastructure Developer
> Phone: 609-258-4161
> 333C 701 Carnegie, Princeton University, Princeton, NJ 08544
>
>
>
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download
> nowhttp://ad.doubleclick.net/ddm/clk/292181274;119417398;o
>
>
>
> _______________________________________________
> DSpace-tech mailing
> listDSpace-tech@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
>
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
