Attendees
General
- Indicates who took minutes -
- Call-in: Google-hangout at:
Goals
- Top-level: Get to 4.0-Beta by Apr 1
- Sprint-level:
- Clustering and clustering performance (Greg Jansen, frank asseg, 1/2 of Scott Prater)
- Unit test coverage > 75% (Ben Pennell, Mike Daines, A. Soroka, et al.)
- Prepare for AuthZ feature sign-off (Ben Pennell, Mike Daines)
- Performance testing with transactions (Ben Pennell, Mike Daines)
- Wiring and Config (A. Soroka)
- Ontology construction and publishing (A. Soroka)
Minutes
Walk through by goals
Clustering
- Scott got "new relic" up and running (monitors nodes, report back to common dashboard), doesn't play well with existing setup
- Fedora Primary is reporting (public node), but ones on private network not reporting
- Some of the nodes can't see the New Relic coordinator, which is causing errors
- Also causing initialization issues with infinispan which go away when the New Relic jars removed.
- Creating a ticket for this issue, will speak with the infinispan group about it
- Greg is going to have a meeting with local sys admins later today to work out puppet issues and handshake issues across nodes. Afterwards he will try to get Benchtool working on the UNC cluster
- Scott discussed Tomcat shutdown problem when running fcrepo on a cluster configuration
- Frank had been using ctrl-c to shut down tomcat, so hadn't run into the problem of the shutdown script not completing
- https://www.pivotaltracker.com/s/projects/684825/stories/65988656
- Frank suspect this may be a modeshape config issue, will investigate further
- Scott got "new relic" up and running (monitors nodes, report back to common dashboard), doesn't play well with existing setup
Wiring and Config
Unit test coverage > 75%
- More unit tests the better, we should try to get close to 100% unit test coverage when submitting a new pull request
Prepare for AuthZ feature sign-off
- We may be close to finished, but we need to take stock of what features have been completed and which use cases have been satisfied
- There are tickets for each of the use cases
- Talk with stakeholders about how to verify that their use case has been satisfied and go about doing so.
Performance testing with transactions
- Using transactions in high throughput situations should be helpful, but we still need to verify that this is the case
- To do this, we should use the existing tools and tests (namely Benchtool) and adapt it to work with transactions for comparison
- Need to determine how to group the actions into reasonable transactions
- Are there use cases for transactions already that we can use as the basis for this determination?
Please create additional tickets by stand up on Tuesday, so that we can prioritize them in that meeting.
