Regular Attendees
- Andrew
- Bill
- Chris (Vacation)
- Dan
- Jonathan
- Danny
General
- Call In To: Free Conference Call HD - DuraCloud Line
- - Indicates who will be taking minutes
Discussion Topic
Topic Discussion Leader Sync Flow Danny DfR Directory Selection Danny OCS Execution Environment Dan DfR 0.2 Release Dan
Actions from last meeting
Action Item |
Assignee |
Status |
|---|---|---|
Create an AMI for running OCS and other services |
Dan |
|
Browse and Select Approach |
Danny |
|
Status
- Jonathan
- Andrew
- Bill
- Chris
- Dan
- Worked on OCS setup and objects
- Danny
Minutes
- DFR-Sync
- will add summary information on "setup complete page"
- once setup is complete: links to status or configuration - sync process will be started automatically
- DFR-92 can be closed.
- Logo/Branding can be determined by Marketing
- DfR 0.2 Release:
- AW: We can either stick to the date and cut it off or we can stick to the functionality and release it when it is finished.
- consensus: let's cut it off -> Straight shot/Release scope to be discussed next Monday/Tuesday
- JM: The hook shot needs to be complete - on the technical side we need to agree what that means.
- Tomorrow's meeting cancelled. We'll reconvene next week when Chris is available.
- DD: Only a subset of the Smithsonian Archeology files are being used: Smithsonian has not made all of the content available.
*OCS Execution Environment: how will it be deployed? - A) Stand-alone : JMS consumer wrapped in an executable jar that instantiates a spring context
- B) OCS wrapped in a spring web app which exposes a REST interface
- for 0.2 the group endorses Option A.
- AW: We can either stick to the date and cut it off or we can stick to the functionality and release it when it is finished.
Other news:
Sidora AMI is available: Dan will IM the AMI name ( one with "v2" in the name)
https://dfr.duracloud.org
Action Items
See above for now.
Action Item |
Assignee |
Status |
|---|---|---|
|
|
|
