...
- William Welling
- Andrew Woods
- Alexander (Sacha) Jerabek
- Benjamin Gross
- Huda Khan
- Ralph O'Flinn
- Brian Lowe
- Nicolas Dickner
- Michel Héon
- Sarbajit Dutta
- Paul Albert
- Don Elsborg
Agenda
- I18n sprint next week
- WCM approach (Sarbajit, Paul)
- Deployment
- WCM's repo
- SDB vs. TDB
- Kubernetes (https://github.com/wcmc-its/vivo-docker.git)
- Ingest
- Deployment
- Drop-in war
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1443 - Third-tier builds?
- Solr configuration
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752 - Two tasks: process for auto-configuration and determining the correct configuration
- Moving Scholars closer to core - next steps
- SelectQueryDocumentModifier
- Entities: Collection, Concept, Document, Organization, Person, Process, and Relationship
- Configuring Solr
- Moving Data Ingest Task Force forward
- WCM approach (Sarbajit, Paul)
- Deployment
- SDB vs. TDB
- Kubernetes
- Ingest
- ReCiter Connect
- Deployment
Future topics
- Vitro JMS messaging approaches - redux
- Which architectural pattern should we take?
- What should the body of the messages be?
- Renaming of 'master' branch? (ZDNet, BBC)
- Guidance from GitHub
- DSpace has done it
- Fedora has done it
- Samvera is doing it
- Incremental development initiatives
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1688 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1751 - Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752
...
Weill Cornell updates
- AWS deployment
- Challenges
- Scalability issues with TDB
- Can only support one VIVO connecting to one TDB
- Ingest: direct to TDB is fast... but using SDB direct for initial
- Reingest is ~3hours with SDB
- Load balancer over VIVO
- CloudFront cache
- 4 CPU 16 GB RAM (t3xlarge)
- ReCiter as backend datasource for publications
- Cost: ~$300/month
- On-prem was ~$40k/year
- 1000 iops