...
Attendees
Indicating note-taker
- Don Elsborg
- Huda Khan
- Ralph O'Flinn
- Andrew Woods Mike Conlon
- Benjamin Gross
- Jim Blake
- Steven McCauley
- Alex ViggioHarry Thakkar
Agenda
- Sprint update
- Demo of:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1685
- Demo of:
- Given Fly-in design overview
- Where are the open questions?
- How can we move the effort forward (2019 sprints, Product Evolution, other)
Search index: approaches for configuration and processes
- Acceptance tests moved to vivo-community, thanks Jim Blake
Status of In-Review tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Soft balls
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1659 - Low-hanging, documentation - Mike Conlon, can you give this one a review?
- Regular balls
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1675 - New
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1670 Kitio Fofack ? Orcid and i18n
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1656 - Is this feature of broader interest?
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1643 - Andrew Woods to look into
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1642 - Mostly trivial, with conversation around Tomcat version support
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1630 - Kitio Fofack to review?
Received
Expand Expand Jira server DuraSpace JIRA jqlQuery filter=14802 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1666 (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1665 - Should be low-hanging
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1663 Where does this stand? What is needed to add more person identifiers to VIVO?
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1644 - Mike Conlon : thoughts on where this stands?
Bugs (1.11)
Expand Jira server DuraSpace JIRA jqlQuery filter=14702 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
Sprint update
Objectives:
Branches for externalizing Solr and ElasticSearch
Get those branches to a point where they can be merged into develop branch
Ralph will be looking at this work this week
Jim provided nested ElasticSearch population code right before retiring
Laser focus goggles on for Ralph
Don: Can we just get rid of the war file?
Andrew: Interim state where not supporting external Solr but taking out internal piece
Harry: build fails - but seems very close - some setting needs to be changed
Building of VIVO Docker
Achieved and still in review
Hope to have a successful demo in the next week or so
Don: Multi-stage VIVO? Others: Yes
Build a war class and copies it over. Can we copy over file to locally so can deploy/ship to cloud?
Andrew: Separate VIVO Docker page that assumes VIVO war file
Don: Practicality? Run one Docker, create WAR and copy locally. Another Docker to create Tomcat container and copies WAR file from local volume and deploys that as a separate step
Andrew: Possible. If someone doesn’t want customizations and just wants to deploy, new Docker process could pull down WAR and then deploy
Don: Current work great for MVP - but not 100% practical yet for the real world. Tooling and scaffolding like Ansible builds - own war file/runtime properties.
Harry: Like mention of Ansible. Why can’t we achieve same objective with Docker compose?
Don: We can. Docker using YAML anyway and Ansible is super set. At our institution, have 3 tier build. Dealing with secret management and customizations. Had used Ansible before. The Docker work gets us close to doing automated custom builds. Perhaps Docker compose could work but can also run compose with Ansible.
Harry: Can’t comment on Ansible since haven’t used it. Docker compose is orchestration so could use that for three/multi-tier application. What we have now is a very basic Docker compose and could go deeper to avail ourselves of deeper features.
If distributing two parts, one creates war, and second uses war shared by Docker compose. Idea that if someone wants to deploy they just use that single compose.
VIVO is sitting in Maven as a war file ready to go or as an image.
Consider this work as an initial step and then we can go further
Don: Between having to maintain VIVO at institution with VIVO work that seems more “vanilla” deployment. The closer these two come together, the more likely I can be involved.
Even with institutions that are at older versions of VIVO, the easier we make it for them to upgrade, easier to bring them into the community effort.
Andrew: community. +1
Andrew: Doing fairly well with this objective. Have Docker compose files.
Solr Docker: done. Solr image and our local usage of image uses Solr configuration expected by VIVO.
ElasticSearch: Not much in this area. Probably easy to do once we actually do it. Have been looking at Solr and MariaDB first.
MariaDB instead of MySQL: done
Documentation: less so. In Duraspace wiki, copied 1.10 documentation into 1.11 space.
Documentation: less so.
Focusing on objective (i) currently. Ideally, good to get this to point where we can share back with community.
Don: project template geared towards multi-tier VIVO. Separate repo for Docker components?
Andrew: yes .Created VIVO Docker 2 repo - have the Docker components. In Andrew’s own github
Harry - is the goal to create a vivo docker in dockerhub?
Ultimately - yes
Point is the VIVO Harry sees in vivo-docker2 fits right into the vision
Fix the build error from the solr-sprint
Could take this image and place it into docker-hub
Could also create a container that takes a local war file and deploys that
So the repo can have a docker-compose.yml file that can get things going
So will the awoods/vivo-docker2 file move into vivo-project or vivocommunity?
Andrew - yes, it will move when ready. Ready to move it now.
Andrew - once sprint-search branch is merged with develop, we should be ready to mint a 1.11 - THis This can be used for a docker that is pushed to docker hub
...