Timestamps are in GMT/BST.
[1:41] * ogres (uid159312@gateway/web/irccloud.com/x-uwftiqcuhqmzqlxe) has joined #duraspace
[2:34] * ogres (uid159312@gateway/web/irccloud.com/x-uwftiqcuhqmzqlxe) Quit (Ping timeout: 256 seconds)
[2:36] * ogres (uid159312@gateway/web/irccloud.com/x-avlsknwrihwyxuaa) has joined #duraspace
[6:39] -orwell.freenode.net- *** Looking up your hostname...
[6:39] -orwell.freenode.net- *** Checking Ident
[6:39] -orwell.freenode.net- *** Found your hostname
[6:39] -orwell.freenode.net- *** No Ident response
[6:39] * DuraLogBot (~PircBot@webster.duraspace.org) has joined #duraspace
[6:39] * Topic is 'Welcome to DuraSpace IRC. This channel is used for formal meetings and is logged - http://irclogs.duraspace.org/'
[6:39] * Set by tdonohue on Thu Sep 15 17:49:38 UTC 2016
[9:30] * ogres (uid159312@gateway/web/irccloud.com/x-avlsknwrihwyxuaa) Quit (Quit: Connection closed for inactivity)
[12:17] * mhwood (~mhwood@mhw.ulib.iupui.edu) has joined #duraspace
[13:47] * ogres (uid159312@gateway/web/irccloud.com/x-jysqjynmyqldcznh) has joined #duraspace
[14:53] <DSpaceSlackBot> <pbecker> dev-mtg. The agenda can be found here: https://wiki.duraspace.org/display/DSPACE/Developers+Meeting+2018-07-25+-+DSpace+and+Docker The only agenda point for today is DSpace-Docker, but we are open for other topics you might want to race.
[14:53] <kompewter> [ Developers Meeting 2018-07-25 - DSpace and Docker - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Developers+Meeting+2018-07-25+-+DSpace+and+Docker
[15:00] <DSpaceSlackBot> <terrywbrady> <here>, hello. Who is present for the meeting today?
[15:00] <DSpaceSlackBot> <mwood> I am
[15:00] <DSpaceSlackBot> <ptrottier> Hello!
[15:00] <DSpaceSlackBot> <jcreel256> I'm here to watch
[15:00] <DSpaceSlackBot> <pbecker> Hello everyone!
[15:01] <DSpaceSlackBot> <pbecker> @terrywbrady and me are leading today’s meeting. Tim is absent.
[15:01] <DSpaceSlackBot> <terrywbrady> It is good to see everyone.
[15:01] <DSpaceSlackBot> <pbecker> Main topic will be DSpace-Docker, but we are open to discuss other topics if you want to.
[15:02] <DSpaceSlackBot> <pbecker> I started with docker some months ago and talked with @terrywbrady about it. He picked up the ball and started to enhance our efforts on this front.
[15:02] <DSpaceSlackBot> <pbecker> He builded most of the part you can find today under http://github.com/DSpace-Labs/DSpace-Docker-Images
[15:02] <kompewter> [ GitHub - DSpace-Labs/DSpace-Docker-Images: Repository for developing and managing published Docker images for DSpace development ] - http://github.com/DSpace-Labs/DSpace-Docker-Images
[15:03] <DSpaceSlackBot> <pbecker> The idea of docker is to package applications into container to make deployment easier, to separate spaces of concerns about and to easily spin up new instances.
[15:04] <DSpaceSlackBot> <terrywbrady> We have the ability to provide a DSpace 4/5/6 instance in a Dcoker container. I am still working on getting the angular piece to work for me.
[15:04] <DSpaceSlackBot> <pbecker> We hope to engage more people into DSpace by making it easier to get a test installation running locally.
[15:05] <DSpaceSlackBot> <terrywbrady> @monikam reviewed the link that Pascal shared and I added some background text describing what we hope to accomplish with Docker. Additional feedback here or in a PR is welcome.
[15:05] <DSpaceSlackBot> <ptrottier> I heard that for Automated Builds, you must place the Dockerfile in the same repo as the project, ie Angular Dockerfile should be in dspace-angular. @terrywbrady Is this another roadblock you encountered?
[15:06] <DSpaceSlackBot> <terrywbrady> @ptrottier and I tested Dockerfile build automation a couple days ago. I did some additional work yesterday and I came to that same conclusion.
[15:07] <DSpaceSlackBot> <pbecker> a little bit of background to what @ptrottier just said: Docker Hub is a webservice where you can easily download pre build containers. @terrywbrady is trying to make it easy for us to offer a container with every official version of DSpace their by having dockerhub building those containers automatically whenever we release a new version of DSpace.
[15:08] <DSpaceSlackBot> <terrywbrady> My hope is to provide an image for every release AND for each supported branch of the code base.
[15:08] <DSpaceSlackBot> <terrywbrady> It would allow anyone to run the current state of dspace-4_x, 5_x, 6_x or master from a simple command line call.
[15:08] <DSpaceSlackBot> <ptrottier> What are everyone's thoughts on giving Docker Hub access to those repositories?
[15:09] <DSpaceSlackBot> <pbecker> @ptrottier let us wait a moment before we go in deeper.
[15:09] <DSpaceSlackBot> <pbecker> Does anyone has question so far about what we want to achieve with docker and what we are doing with docker currently?
[15:10] <DSpaceSlackBot> <mwood> How does this relate to Vagrant-DSpace?
[15:11] <DSpaceSlackBot> <terrywbrady> (My hope is that we will document a set of recommendations in our meeting today and then share those recommendations with the DSpace Committer team).
[15:11] <DSpaceSlackBot> <pbecker> As far as I know, Vagrant is more oriented towards development. It helps you to setup an development environment.
[15:11] <DSpaceSlackBot> <pbecker> Docker is used for production as well as for development.
[15:11] <DSpaceSlackBot> <terrywbrady> @mwood, I do not know Vagrant well. I think this could replace the need for Vagrant.
[15:12] <DSpaceSlackBot> <pbecker> Docker seems to me much more lightway and easier to use than vagrant.
[15:12] <DSpaceSlackBot> <pbecker> While vagrant spins up a new virtual machine for each instance, Docker follows a concept of containers.
[15:13] <DSpaceSlackBot> <pbecker> Containers feel a bit like a virtual machine on their own, but it is integrated in the host system in another way and therefor more lightweighted.
[15:13] <DSpaceSlackBot> <pbecker> Your question is going in the right direction as in the end both helps you to setup an installation of DSpace as easy as possiple.
[15:13] <DSpaceSlackBot> <terrywbrady> Does anyone on the call know of another library/institution that has utilized Docker extensively? It would be good to validate our plans with someone else from the library tech community.
[15:13] <DSpaceSlackBot> <pbecker> The way they are doing that differs.
[15:14] <DSpaceSlackBot> <mwood> Thanks.
[15:14] <DSpaceSlackBot> <terrywbrady> I failed in my past attempt to use Vagrant. I have found Docker easy to get up an running. I am a bit overwhelmed by everything that might be possible with it.
[15:16] <DSpaceSlackBot> <terrywbrady> I may post to the Code4Lib list to see if someone can recommend another library/open source project that has attempted to leverage Docker.
[15:16] <DSpaceSlackBot> <pbecker> @mwood https://docs.docker.com/get-started/#containers-and-virtual-machines explains the whole container vs. virtual machine deeper
[15:16] <kompewter> [ Get Started, Part 1: Orientation and setup | Docker Documentation ] - https://docs.docker.com/get-started/#containers-and-virtual-machines
[15:18] <DSpaceSlackBot> <terrywbrady> Based on my experimentation so far, I have found it easy to distribute/share the DSpace software images. I am not sure if there is a good mechanism to share software + test data via Docker.
[15:18] <DSpaceSlackBot> <pbecker> Let me try to give you a short abstract how docker works: You have a Dockerfile that is basically a script running all the things you need to do to start the application you want to be run in the container.
[15:19] <DSpaceSlackBot> <pbecker> For each application (tomcat, postgres, …) you have one container.
[15:19] <DSpaceSlackBot> <pbecker> You have may have a docker-compose file that describes how all the containers are started.
[15:19] <DSpaceSlackBot> <pbecker> Docker first has to “build” the “image”. It is basically running the instructions in all the Dockerfiles.
[15:19] <DSpaceSlackBot> <pbecker> docker-compose is the starting all the pre build images.
[15:20] <DSpaceSlackBot> <pbecker> Docker Hub is the place to exchange pre build images, so that not everyone hast to build them locally.
[15:20] <DSpaceSlackBot> <pbecker> @terrywbrady is working on letting docker hub build those images for us.
[15:21] <DSpaceSlackBot> <terrywbrady> (and @ptrottier too)
[15:21] <DSpaceSlackBot> <pbecker> sorry, thanks for adding that.
[15:21] <DSpaceSlackBot> <pbecker> The question @ptrottier raised is the following: To let docker hub detect whenever it needs to rebuild the images, because we change one of our branches, it needs to be integrated in our github repository.
[15:21] <DSpaceSlackBot> <pbecker> Therefore we would like to give Docker-Hub access to our github repository.
[15:22] <DSpaceSlackBot> <terrywbrady> Like GitHub, DockerHub is a commercial service. They provide a lot of useful stuff for free and then offer paid services in addition.
[15:22] <DSpaceSlackBot> <pbecker> Till yesterday I thougt it would be enough to give it access to DSpace-Labs/Docker-Images, but as @ptrottier and @terrywbrady told us at the beginning of the meeting it looks like we need to include our Dockerfiles into DSpace/DSpace and include docker hub over there.
[15:23] <DSpaceSlackBot> <pbecker> @ptrottier @terrywbrady right?
[15:23] <DSpaceSlackBot> <ptrottier> Yes, both https://github.com/DSpace/DSpace and https://github.com/DSpace/dspace-angular
[15:23] <kompewter> [ GitHub - DSpace/DSpace: (Official) The DSpace digital asset management system that powers your Institutional Repository ] - https://github.com/DSpace/DSpace
[15:23] <DSpaceSlackBot> <terrywbrady> Each user with a DockerHub account has the ability to configure one simultaneous automated build. Paid accounts can run multiple builds in parallel. Based on some testing yesterday, a DSpace Docker image build takes 30 min to run.
[15:23] <kompewter> [ GitHub - DSpace/dspace-angular: Angular UI for DSpace 7. See the README below for links to resources and documentation. ] - https://github.com/DSpace/dspace-angular
[15:24] <DSpaceSlackBot> <terrywbrady> If we want to trigger the build to run when a branch is updated (master, dspace-6_x), I believe we will want the Dockerfile to be hosted within the code branch.
[15:24] <DSpaceSlackBot> <terrywbrady> As we have been learning to use Docker, we have housed the Dockerfile source code in an DSpace-Labs repo.
[15:26] <DSpaceSlackBot> <terrywbrady> It does require us to grant some permissions to DockerHub from the GitHub repo, so we will want to review the implications of those permissions.
[15:26] <DSpaceSlackBot> <pbecker> It’s comparable to Travis CI.
[15:26] <DSpaceSlackBot> <pbecker> Travis CI also needs to be integrated in the github repository, you’re using to host your code.
[15:27] <DSpaceSlackBot> <terrywbrady> Do we (DSpace) pay for Travis?
[15:27] <DSpaceSlackBot> <pbecker> I think we use the free version for Open Source projects.
[15:27] <DSpaceSlackBot> <pbecker> Before moving the Dockerfiles over to DSpace/DSpace and discussing if we integrate Docker-Hub over there, we should be sure how the automatic builds are working.
[15:28] <DSpaceSlackBot> <pbecker> @terrywbrady were you able to resolve all your questions already?
[15:29] <DSpaceSlackBot> <pbecker> I think part of the idea of todays meeting was to push out the message, that we are working on these things and would be happy, if anyone familiar with docker and maybe docker hub or anyone interested in this would contact one of us in dspace-docker
[15:30] <DSpaceSlackBot> <terrywbrady> It was a good leaning exercise yesterday. I encountered 3 issues with the automated builds. (1)permissions - as Patrick described (2) I had configured the docker build to rely on a running postgres image which is impossible when automated (3) passing a branch to the build.
[15:31] <DSpaceSlackBot> <terrywbrady> For (1), I cloned DSpace to my personal account and ran the build there. For (2), I changed the ant task to drop the database dependency. See: https://github.com/DSpace-Labs/DSpace-Docker-Images/pull/42 For (3), I see that the docker build command can take a git URL as a parameter. I want to see if that can help resolve this issue.
[15:31] <kompewter> [ Simplify image build dependency by terrywbradyC9 · Pull Request #42 · DSpace-Labs/DSpace-Docker-Images · GitHub ] - https://github.com/DSpace-Labs/DSpace-Docker-Images/pull/42
[15:33] <DSpaceSlackBot> <terrywbrady> I just shared a bunch of info. Is it making sense to you all?
[15:33] <DSpaceSlackBot> <ptrottier> I wonder if we could get Travis to build the Docker images and simply push to DockerHub via the account credentials.
[15:34] <DSpaceSlackBot> Action: ptrottier is reading over https://ops.tips/blog/travis-ci-push-docker-image/
[15:34] <kompewter> [ Pushing Docker images right from Travis-CI | OpsTips ] - https://ops.tips/blog/travis-ci-push-docker-image/
[15:34] <DSpaceSlackBot> <pbecker> @mwood It is to me. But it sounds like we still need to continue working this out in a personal repo, before we really can start the discussion about adding this to our official main repo. Right?
[15:36] <DSpaceSlackBot> <terrywbrady> We still have some details to work through, but I think that they are solve-able. I have not yet read the link that Patrick shared.
[15:36] <DSpaceSlackBot> <terrywbrady> That is a different approach.
[15:38] <DSpaceSlackBot> <terrywbrady> Integrating with travis would make it easier to build images for PR's.
[15:39] <DSpaceSlackBot> <terrywbrady> @ptrottier do you have an opinion on which approach would work best?
[15:40] <DSpaceSlackBot> <pbecker> Travis is definitely something we should check out.
[15:40] <DSpaceSlackBot> <pbecker> (to build the images)
[15:40] <DSpaceSlackBot> <ptrottier> It seems to nullify the permissions problem (#1)
[15:41] <DSpaceSlackBot> <pbecker> We have a hard limit of 3 GB of concurrent memory use in Travis. So we would add the docker build after our maven tests. This would enlarge the time a travis build needs to run.
[15:41] <DSpaceSlackBot> <terrywbrady> I will attempt to summarize some of the outstanding decisions to be made on a wiki page and will post updates to dspace-docker
[15:43] <DSpaceSlackBot> <terrywbrady> It would be great to get feedback on my PR's for the Docker repo. https://github.com/DSpace-Labs/DSpace-Docker-Images/pulls
[15:43] <kompewter> [ Pull Requests · DSpace-Labs/DSpace-Docker-Images · GitHub ] - https://github.com/DSpace-Labs/DSpace-Docker-Images/pulls
[15:43] <DSpaceSlackBot> <pbecker> I have the feeling we gave a good starting point for the discussion. As @tdonohue is not here and people might want to follow the links and information we gave to day, we might want to continue this discussion in one of our next meetings <here>. Is there anything anyone wants to add to the docker topic today or shall we open the floor for other topics?
[15:44] <DSpaceSlackBot> <pbecker> One last thing from my side: From what I saw @terrywbrady and @ptrottier described very well what to do, to use our docker images. It is really easy, so go and try it out!
[15:44] <DSpaceSlackBot> <terrywbrady> Once you have Docker on your desktop (Mac, Win10 or Linux), our tutorial pages should be easy to follow.
[15:45] <DSpaceSlackBot> <pbecker> If no one disagrees, I’d like to stop the discussion here. We have 15 minutes left for other topics. Does anyone has anything on his, her or its mind?
[15:46] <DSpaceSlackBot> <pbecker> That is your chance to ask people about the review you’re waiting so long for or to ask questions if you’re trying to develop something and want to know if you’re on a good track…
[15:47] <DSpaceSlackBot> <terrywbrady> The Dev Show and Tell is next week.
[15:48] <DSpaceSlackBot> <pbecker> seems like everyone <here> is reading the README on https://github.com/DSpace-Labs/DSpace-Docker-Images :slightly_smiling_face:
[15:48] <kompewter> [ GitHub - DSpace-Labs/DSpace-Docker-Images: Repository for developing and managing published Docker images for DSpace development ] - https://github.com/DSpace-Labs/DSpace-Docker-Images
[15:48] <DSpaceSlackBot> <terrywbrady> The July Developer Show and Tell will focus on Tools for working with a REST API. The meeting agenda topics apply to the REST API for DSpace 5, 6, and 7. Agenda Art Lowell will share how he uses Postman to query the DSpace SOLR repositories. Terry Brady will demonstrate how to authenticate to the DSpace 7 REST API in Postman. James Creel will Share the Texas A&M MAGPIE (Metadata Assignment GUI Providing
[15:48] <DSpaceSlackBot> Logistics https://wiki.duraspace.org/display/DSPACE/Dev+Show+and+Tell+-+July+31%2C+2018+-+1500UTC+-+REST+API+Tools The August 28 Developer Show and Tell will focus on "DSpace on DockerHub". https://wiki.duraspace.org/display/DSPACE/Dev+Show+and+Tell+-+Aug+28%2C+2018+-+1500UTC+-+DSpace+On+DockerHub
[15:48] <DSpaceSlackBot> <pbecker> @terrywbrady Do you want to advertise the topic of next weeks show and tell?
[15:48] <kompewter> [ Dev Show and Tell - July 31, 2018 - 1500UTC - REST API Tools - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Dev+Show+and+Tell+-+July+31%2C+2018+-+1500UTC+-+REST+API+Tools
[15:48] <kompewter> [ Dev Show and Tell - Aug 28, 2018 - 1500UTC - DSpace On DockerHub - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/Dev+Show+and+Tell+-+Aug+28%2C+2018+-+1500UTC+-+DSpace+On+DockerHub
[15:48] <DSpaceSlackBot> <mwood> https://github.com/DSpace/DSpace/pull/2031 has one approval. https://github.com/DSpace/DSpace/pull/2042 the same.
[15:48] <kompewter> [ [DS-3895] Bitstream size can't be referenced in HQL queries by mwoodiupui · Pull Request #2031 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/2031
[15:48] <kompewter> [ [DS-3895] Bitstream size can't be referenced in HQL queries by mwoodiupui · Pull Request #2042 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/2042
[15:49] <DSpaceSlackBot> <terrywbrady> Nice DSpace emoji @pbecker
[15:49] <DSpaceSlackBot> <terrywbrady> :dspace:
[15:50] <DSpaceSlackBot> Action: ptrottier waves
[15:51] <DSpaceSlackBot> <pbecker> @mwood 2042 is at +2 now.
[15:52] <DSpaceSlackBot> <pbecker> If there is nothing else, I would end the meeting.
[15:52] <DSpaceSlackBot> <pbecker> Have a great day everyone!
[15:52] <DSpaceSlackBot> <terrywbrady> Thanks for the good discussion. Have a good week!
[15:52] <DSpaceSlackBot> <mwood> Thanks all.
[15:53] <DSpaceSlackBot> <pbecker> @mwood 2031 is at +2 now as well.
[15:53] <DSpaceSlackBot> <mwood> Thank you for the reviews!
[15:55] <DSpaceSlackBot> <pbecker> thank you for the PRs!
[20:39] * mhwood (~mhwood@mhw.ulib.iupui.edu) Quit (Remote host closed the connection)
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.