LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  April 2016

CODE4LIB April 2016

Subject:

Re: Islandora & Vagrant - Development use only?

From:

"Harnum, Alan" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 8 Apr 2016 13:10:51 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

While I can’t comment on the Islandora piece, I’ll make the following comments about Vagrant in the context of how we use it as part of our development and ops process:

- Vagrant is used as described below for “disposable environments and consistent workflow” for testing our automation scripts and tools - we use fairly barebones Vagrantfiles to bring up VMs that match our production environment targets, then provision those with the same Ansible playbook intended to be used in production. This lets us rapidly develop and test our automation before turning it loose on an environment outside our local machines

- production servers are also virtual machines, using KVM on Red Hat; these get provisioned with the same Ansible playbooks developed initially using Vagrant. There’s nothing inherently unsound about the idea of running using virtual machines in production, provided you understand the reasons behind and accept the overhead of doing so (in our case, our production VMs are launched and managed on a large, dedicated cluster intended for virtualization)

- it’s possible the idea is to use Vagrant as a virtual machine management solution in production; I agree with others below that this isn’t an optimal solution, nor I think would Vagrant’s creators (I personally Hashicorp has blurred the lines on this in recent years as they try to extend their business model, which may be where some of this is coming from)

- if the position is that Vagrant is the same class of environment isolation tool as RVM or virtualenv, that’s a misunderstanding; RVM or virtualenv create isolated environments with very little overhead running on the same system, while Vagrant creates virtual machines with all the overhead that entails

ALAN HARNUM
SENIOR INCLUSIVE DEVELOPER
INCLUSIVE DESIGN RESEARCH CENTRE, OCAD UNIVERSITY

E [log in to unmask]<mailto:[log in to unmask]>

On Apr 7, 2016, at 1:56 PM, Annamarie C Klose <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Thank you to everyone who provided feedback on this issue. I've posted my question to the Islandora Google group, as well. I'll be meeting with my university's IT department on Monday. I appreciate your help!

Anna

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Cindi Blyberg
Sent: Wednesday, April 06, 2016 5:46 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [CODE4LIB] Islandora & Vagrant - Development use only?

Cary, the snippet to your email as shown in my inbox only showed the first sentence. Glad to read the rest! :)

On Wed, Apr 6, 2016 at 2:01 PM, Cary Gordon <[log in to unmask]<mailto:[log in to unmask]>> wrote:

I disagree with the statement that "Vagrant is not a good idea for
production.” Vagrant is a terrible idea for production, and it is not
designed for that.

We use Ansible to build Islandora, and, after three years of talking
about it we are starting to use it with Docker. We are an AWS shop, so
we use Docker with AWS elastic container service, which could come in
handy if one of your archives gets slashdotted.

Cary

On Apr 6, 2016, at 8:53 AM, Chris Fitzpatrick
<[log in to unmask]<mailto:[log in to unmask]>>
wrote:

Vagrant is not a good idea for production. It's really for people to
work against a copy of the production environment.
Like you can use Vagrant, then update a ansible or puppet or chef
script then deploy that to yr VM.
Hashicorp is making something called Otto which is supposed to
replace Vagrant for end-to-end deployments like this, but that's in alpha now.

Vagrant isn't  like virtualenv at all. Virtualenv is a way to
maintain Python dependencies by mucking around with some environment variables.
It's
more like Ruby's bundler.

It's kinda more like Docker. Docker makes linux containers. Nobody
knows what those are, but they work great.

I've seen Vagrant used in production and it supposedly worked well
but
the
guy who set it up left and things went bad. It wasn't a performance
issue,
it's just really hard for the replacement to figure out what's going on.
Use Vagrant with Ansible/Puppet/Chef. Or use Docker. Or use all of
that, for the win.



On Wed, Apr 6, 2016 at 3:55 PM, Francis Kayiwa <[log in to unmask]<mailto:[log in to unmask]>> wrote:

On 4/6/16 9:49 AM, Annamarie C Klose wrote:

Hi, all,

Can anyone provide a technical explanation as to why it is not
appropriate to install Islandora on a public server with Vagrant?
Despite
all the documentation instructing that Vagrant is for development
only, my
university's IT department thinks Vagrant makes Islandora more
secure
for
production use. They have also stated "Vagrant is used to keep
dependencies
separate on machines in the same way Pythons Virtualenv or Ruby's
Docker
is." Unfortunately, secure networking is outside of my expertise.
I'm concerned that Vagrant's virtualization is a poor substitute
for the
real
thing. Before I add hundreds of records to Islandora, I'd like to
make
sure
that I'm building my library's digital collections on a steady
foundation.
Any advice and/or explanations to give IT is welcome.



If we agree  that your University IT are the Operations people find
the nicest way to tell them how the developers of Vagrant view the
tool
below

https://www.vagrantup.com/docs/why-vagrant/

Specifically. "...If you are an operations engineer, Vagrant gives
you a disposable environment and consistent workflow for developing
and
testing
infrastructure management scripts..."

You are also correct in being wary about having a production
application running on Vagrant. A part of me wants to test that
just for laughs,
but it
will be painful to set up for them and the performance will
horrible for you.

Cheers,
./fxk

--
"Anyone attempting to generate random numbers by deterministic
means is, of course, living in a state of sin."
-- John Von Neumann



Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager