Difference between revisions of "Meetings/Karbor"
< Meetings
(→Agenda (2015-12-22 1400 UTC)) |
(→Agenda (2015-1-26 1400 UTC)) |
||
Line 28: | Line 28: | ||
**Base Service class | **Base Service class | ||
***https://review.openstack.org/#/c/259901/ | ***https://review.openstack.org/#/c/259901/ | ||
− | === Agenda ( | + | === Agenda (2016-1-26 1400 UTC) === |
*Open Issues | *Open Issues | ||
**whether to build task flow inside protection plugin or out side of it? | **whether to build task flow inside protection plugin or out side of it? | ||
**whether restore procedure needs first import metadata from bank? | **whether restore procedure needs first import metadata from bank? | ||
**whether checkpoint should be persisted with its brief metadata in API layer DB? | **whether checkpoint should be persisted with its brief metadata in API layer DB? |
Revision as of 07:03, 26 January 2016
Contents
Biweekly Smaug meeting
The Smaug project team holds a meeting in #openstack-meeting at:
- Tuesday at 1400 UTC each even week
Agenda (2016-01-12 1400 UTC)
- API, Last call for comments
- Pluggable Proection Provider QA
- Protection Service tasks
- Scheduler Service Design Status
Everyone is welcome, feel free to add topics before or at the beginning of meetings.
Agenda (2015-12-22 1400 UTC)
- Smaug Overview
- Proposed Smaug API v1.0
- Open Issues
- dependency between resources: will/how smaug protect/store the attachment between volume to vm, vm to network etc.
- Scheduler service design status
- Protection service design status
- Boilerplate un-started generic infrastructure tasks
https://etherpad.openstack.org/p/smaug-bootsrap
- patches Open for review
- Base data abstraction layer
- Base Service class
Agenda (2016-1-26 1400 UTC)
- Open Issues
- whether to build task flow inside protection plugin or out side of it?
- whether restore procedure needs first import metadata from bank?
- whether checkpoint should be persisted with its brief metadata in API layer DB?