Regular Attendees
- Andrew
- Bill
- Chris
- Dan
- Jonathan
- Danny
General
- Call In To: Free Conference Call HD - DuraCloud Line
- - Indicates who will be taking minutes
Discussion Topic
Advanced Tables - Table Plus | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Actions from last meeting
Action Item | Assignee | Status |
---|---|---|
Improve the SI AMI | Dan |
|
Try the sync rate utility and report your results | All |
|
Status
- Jonathan
- Andrew
- Bill
- Chris
- DFR CloudSync instance now up at http://dfrtest.duracloud.org:18081/cloudsync.
- Dan
- Jetty for ITs has been added
- Basic MDB execution environment (BDD/TDD) has been added
- The "internal" producer IT (not using a live DuraCloud) is not working (will drop for now if no success today)
- Will not include an IT Fedora this iteration
- Still working on the objects
- Danny
Minutes
SiDora
- Call tomorrow at 10am Eastern with Thorny and Mark Leggot (DuraCloud line)
- Topic: How to move forward with SiDora
OCS testing environment
- Dan: Continuing to flesh out the execution environment, particularly trying to get the build to work properly
- Trying to get an integration test setup that can make use of a locally deployed Jetty, and not depend on an external DuraCloud
- Message broker is running, having some trouble getting it to stop. Trouble getting messages to be sent/received properly.
- Chris/Bill: Good to get more granular integration tests before getting into full end-to-end integration tests
- Will eventually need some end-to-end test
- Two main granular integration tests (for OCS):
- Send/receive message and push through OCS to end up with a Fedora object
- Start with a Fedora object, push it into SiDora, make calls to be able to retrieve it again
- Dan: Question to work out: How much wiring is done in Spring vs in code
- Would like pointers to how this is done in DuraCloud (todo: Bill)
- Using Spring JUnit runner, allows for using annotations for config
- We considered that as part of DuraCloud, but moved away from it
- Dan: Planning to make the call to cut off further test framework investigation by tomorrow
OCS object creation
- Still needs to be smoothed out
- Maybe half a day of work to get that finished up
- Dan to take this on, with a bit of help from Chris
Release 0.2
- Chris working on setting up the AMI for hookshot demo
- Dan: looking at another 2 days or so to get the demo in shape
- How solid does the release date need to be?
- Jonathan: Need to show a demo, but not for another 2 weeks
- Need to get moving on planning for 0.3 release
- Dan: Would like an additional 2 days to be able to get the testing worked out prior to release
- Release date pushed to Thursday
Face-to-face meeting
- Goal is to plan out 0.3 and 0.4 releases
- Plan is to meet Sunday and Monday before BHR (Sept 9-10)
0.3 planning
- Need to meet to start this work as soon as possible
- Technical Meeting: Next Monday, 11am - 1pm
- ToDo for everyone: Begin to consider which items need to be worked in the next round
- Will also need to scope the work for 0.4
- Meet with Jonathan: Next Wednesday, 10am - 12pm
Sync tool update
- We have a functioning sync tool
- You can run through the wizard, and start things up
- Can't yet edit the configuration (can be re-set)
- Still need to set it up to be runnable as a Jar
- Some parts have been styled, quite a bit of work to do here (it is functional, though)
- Next task is to get the styling in order
- Should have something demo-able in the next few weeks
Action Items
See above for now.
Action Item | Assignee | Status |
---|---|---|
Send pointers to DuraCloud messaging code to Dan | Bill |
|
Review jira items and plans in prep for defining the 0.3 goals | All |
|