Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- NEW Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
Attendees
- Unknown User (acoburn)
- Bethany Seeger
- Jared Whiklo
- Nick Ruest
- James R. Griffin III
- Yinlin Chen
- Aaron Birkland
Agenda
Special Topic: Vagrant? Packer? Docker? what are Fedora's next steps?
- What are the target uses of a F4 VM?
- Do we or can we have a base box?
- Institutional Use Cases
- Lafayette College Libraries
- Using Vagrant with Puppet and vagrant-librarian-puppet for development
- Using OpenShift with Docker for deployment
- Lafayette College Libraries
- ...
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
- What are some use cases for Vagrant images?
- Sane environment for teaching & instruction
- Documentation of what's involved in creating certain integrations
- Rapidly provisioning dev environment. Vagrant on laptops have been workable options where institutional resources are unreasonably constrained/restricted
- Islandora creates a 'base' box. Would it be useful to have one for Fedora, what would be in it?
- Java 8, Maven, Karaf, Tomcat, Fuseki?, Solr?
- How does one manage versions of all these?
- Islandora has repo for building new boxes
- There is a way for Vagrant to notify user when updates are available
- Should a base box be Debian/Ubuntu based?
- Amherst uses CentOS, but really it doesn't matter
- When using Docker, the issue becomes irrelevant
- Phase I: Consensus for base box, basic image
- Nick Ruest, Jared Whiklo, James R. Griffin III volunteer to contribute to this
- Islandora makes a very simple base box, relying on configuration files and shell scripts rather than frameworks where possible
- .. but when it comes to moving to production, value of adopting tools/frameworks like Ansible, Chef, Puppet, etc are making it more worthwhile to invest the effort
- Redhat tooling strongly leverages Puppet
- With Puppet, resolving intermodule dependencies has been strong. Works particularly well in combination with 'acceptance testing' frameworks for spec-ing and launching VMs
- Phase II: Pull in frameworks and management tools (e.g. Packer, Docker, Ansible, Chef, Puppet, etc)?
- Does anybody have expertise in this area?
- Maybe contact to Alicia Cozine et al. They gave a presentation at HydraConnect, and may even have some publicly available images to work off of
- Welcome Nick Ruest to the team!